Storage system and storage control apparatus

ABSTRACT

A storage system has a RAID group configured by storage media, a system controller with a processor, a buffer memory coupled to storage devices and the processor by a communication network, and a cache memory coupled to the processor and the buffer memory by the network. A processor that stores first data, which is related to a write request from a host computer, in a cache memory, specifies a first storage device for storing data before update, which is data obtained before updating the first data, and transfers the first data to the specified first storage device. A first device controller transmits the first data and second data based on the data before update, from the first storage device to the system controller. The processor stores the second data in the buffer memory, specifies a second storage device, and transfers the stored second data to the specified second storage device.

TECHNICAL FIELD

The present invention relates to technology for computing a redundancycode stored in a storage device.

BACKGROUND ART

There is known a storage system that has a plurality of disk devices anda storage controller for controlling these disk devices, wherein each ofthe disk devices functions to create a parity (Patent Literature 1, forexample). In this storage system, the storage controller transmitsupdated data (new data) to a disk device storing data before update (olddata). From the old data and the new data, the disk device creates anintermediate value (intermediate parity) used for creating a new parity,writes the new data into the disk thereof, and empties the storageregion in which the old data was stored, to have a blank region. Thedisk device transmits this intermediate parity to the storagecontroller. The storage controller stores the intermediate parity in acache memory and nonvolatile memory of the storage controller. Thestorage controller then reads the intermediate parity from the cachememory and transmits the intermediate parity to a disk device storing anold parity. This disk device creates a new parity from the receivedintermediate parity and the old parity, writes the new parity into thedisk thereof, and empties the storage region in which the old parity wasstored, to have a blank region.

CITATION LIST Patent Literature

-   [PTL (Patent Literature) 1]-   U.S. Pat. No. 6,098,191

SUMMARY OF INVENTION Technical Problem

In Patent Literature 1, the process for storing the intermediate parityin both the cache memory and the nonvolatile memory increases the loadimposed on the storage controller. This makes the performance of thestorage controller a bottleneck, deteriorating the performance of thestorage controller. However, storing the intermediate parity in eitherthe cache memory or the nonvolatile memory can cause data loss in caseof a system fault.

Solution to Problem

A storage system as one aspect of the present invention has: a pluralityof storage devices, each of which has a plurality of storage media and adevice controller for controlling the plurality of storage media and hasa RAID group configured by the plurality of storage media; and a systemcontroller that has a processor, a buffer memory coupled to theplurality of storage devices and the processor by a predeterminedcommunication network, and a cache memory coupled to the processor andthe buffer memory by the predetermined communication network.

The processor stores first data, which is related to a write requestfrom a host computer, in the cache memory, specifies from the pluralityof storage devices a first storage device for storing data beforeupdate, which is data obtained before updating the first data, andtransfers the first data to the specified first storage device. A firstdevice controller of the first storage device transmits the first dataand second data based on the data before update, from the first storagedevice to the system controller.

The processor stores the second data in the buffer memory, specifies asecond storage device from the plurality of storage devices, andtransfers the stored second data to the specified second storage device.The processor also manages a process stage information item indicating astage of a process performed on the write request.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a configuration of a storage system.

FIG. 2 shows a configuration of an FMPK 144.

FIG. 3 shows a menu screen.

FIG. 4 shows a write process according to Embodiment 1.

FIG. 5 shows an operation performed by an MP 121 upon reception of awrite command, according to Embodiment 1.

FIG. 6 shows an operation performed by the MP 121 after the execution ofwriting into a buffer 113 of an FEPK 110, according to Embodiment 1.

FIG. 7 shows an operation performed by the MP 121 after the execution ofwriting into a CM 131, according to Embodiment 1.

FIG. 8 shows an operation performed by the MP 121 after a write commandresponse is obtained, according to Embodiment 1.

FIG. 9 shows an operation performed by the MP 121 after the execution ofwriting into a BEPK 140, according to Embodiment 1.

FIG. 10 shows an operation performed by the MP 121 after a normal end ofa new data transmission command, according to Embodiment 1.

FIG. 11 shows an operation performed by the MP 121 after a normal end ofan intermediate parity reception command, according to Embodiment 1.

FIG. 12 shows an operation performed by the MP 121 after a normal end ofan intermediate parity transmission command, according to Embodiment 1.

FIG. 13 shows an operation performed by the MP 121 after a normal end ofa new data commit command transmitted to a data FMPK 144A, according toEmbodiment 1.

FIG. 14 shows an operation performed by the MP 121 after a normal end ofthe new data commit command transmitted to a parity FMPK 144P, accordingto Embodiment 1.

FIG. 15 shows an operation performed by the MP 121 upon an occurrence ofan MP fault, according to Embodiment 1.

FIG. 16 shows an operation performed by the MP 121 in the case wherethere is a registration in a post-parity generation queue, according toEmbodiment 1.

FIG. 17 shows a transition write process performed upon the occurrenceof the MP fault in a pre-parity generation stage, according toEmbodiment 1.

FIG. 18 shows the transition write process performed upon the occurrenceof the MP fault in a post-parity generation stage, according toEmbodiment 1.

FIG. 19 shows a FMPK state 1, according to Embodiment 1.

FIG. 20 shows a FMPK state 2, according to Embodiment 1.

FIG. 21 shows an operation performed based on the new data transmissioncommand under the FMPK state 1, according to Embodiment 1.

FIG. 22 shows an operation performed based on the new data transmissioncommand under the FMPK state 2, according to Embodiment 1.

FIG. 23 shows an operation performed based on the intermediate parityreception command under the FMPK state 1, according to Embodiment 1.

FIG. 24 shows an operation performed based on the intermediate parityreception command under the FMPK state 2, according to Embodiment 1.

FIG. 25 shows an operation performed based on the intermediate paritytransmission command under the FMPK state 1, according to Embodiment 1.

FIG. 26 shows an operation performed based on the intermediate paritytransmission command under the FMPK state 2, according to Embodiment 1.

FIG. 27 shows an operation performed based on the new data commitcommand under the FMPK state 1, according to Embodiment 1.

FIG. 28 shows an operation performed based on the new data commitcommand under the FMPK state 2, according to Embodiment 1.

FIG. 29 shows an operation performed based on a normal read commandunder the FMPK state 1, according to Embodiment 1.

FIG. 30 shows an operation performed based on the normal read commandunder the FMPK state 2, according to Embodiment 1.

FIG. 31 shows an operation performed based on a normal write commandunder the FMPK state 1, according to Embodiment 1.

FIG. 32 shows an operation performed based on the normal write commandunder the FMPK state 2, according to Embodiment 1.

FIG. 33 shows transitions of the system states, according to Embodiment1.

FIG. 34 shows an arrangement of data in a system state 1, according toEmbodiment 1.

FIG. 35 shows an arrangement of data in a system state 2, according toEmbodiment 1.

FIG. 36 shows an arrangement of data in a system state 3, according toEmbodiment 1.

FIG. 37 shows an arrangement of data in a system state 4, according toEmbodiment 1.

FIG. 38 shows an arrangement of data in a system state 5, according toEmbodiment 1.

FIG. 39 shows an arrangement of data in a system state 6, according toEmbodiment 1.

FIG. 40 shows an arrangement of data in a system state 7, according toEmbodiment 1.

FIG. 41 shows an arrangement of data in a system state a, according toEmbodiment 1.

FIG. 42 shows an arrangement of data in a system state A, according toEmbodiment 1.

FIG. 43 shows an arrangement of data in a system state B, according toEmbodiment 1.

FIG. 44 shows an arrangement of data in a system state C, according toEmbodiment 1.

FIG. 45 shows an arrangement of data in a system state D, according toEmbodiment 1.

FIG. 46 shows an arrangement of data in a system state E, according toEmbodiment 1.

FIG. 47 shows an arrangement of data in a system state F, according toEmbodiment 1.

FIG. 48 shows an arrangement of data in a system state b, according toEmbodiment 1.

FIG. 49 shows an arrangement of data in a system state c, according toEmbodiment 1.

FIG. 50 shows an arrangement of data in a system state G, according toEmbodiment 1.

FIG. 51 shows an arrangement of data in a system state e, according toEmbodiment 1.

FIG. 52 shows an arrangement of data in a system state f, according toEmbodiment 1.

FIG. 53 shows an arrangement of data in a system state I, according toEmbodiment 1.

FIG. 54 shows a write process according to Embodiment 2.

FIG. 55 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 2.

FIG. 56 shows the transition write process performed upon the occurrenceof the MP fault in a mid-stage of data media update, according toEmbodiment 2.

FIG. 57 shows the transition write process performed upon the occurrenceof the MP fault in a mid-stage of parity media update, according toEmbodiment 2.

FIG. 58 shows the transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 2.

FIG. 59 shows an operation performed based on the normal read command,according to Embodiment 2.

FIG. 60 shows an operation performed based on the normal write command,according to Embodiment 2.

FIG. 61 shows an operation performed based on an XDWRITE command,according to Embodiment 2.

FIG. 62 shows an operation performed based on an XDREAD command,according to Embodiment 2.

FIG. 63 shows an operation performed based on an XPWRITE command,according to Embodiment 2.

FIG. 64 shows a write process according to Embodiment 3.

FIG. 65 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 3.

FIG. 66 shows the transition write process performed upon the occurrenceof the MP fault in the mid-stage of data media update, according toEmbodiment 3.

FIG. 67 shows the transition write process performed upon the occurrenceof the MP fault in the mid-stage of parity media update, according toEmbodiment 3.

FIG. 68 shows a write process according to Embodiment 4.

FIG. 69 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 4.

FIG. 70 shows the transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 4.

FIG. 71 shows a FMPK state 1a according to Embodiment 4.

FIG. 72 shows a FMPK state 2a according to Embodiment 4.

FIG. 73 shows a FMPK state 3a according to Embodiment 4.

FIG. 74 shows an operation performed based on an old data transmissioncommand under the FMPK state 1a, according to Embodiment 4.

FIG. 75 shows an operation performed based on the old data transmissioncommand under the FMPK state 2a, according to Embodiment 4.

FIG. 76 shows an operation performed based on the old data transmissioncommand under the FMPK state 3a, according to Embodiment 4.

FIG. 77 shows an operation performed based on a new data transmissioncommand under the FMPK state 1a, according to Embodiment 4.

FIG. 78 shows an operation performed based on the new data transmissioncommand under the FMPK state 2a, according to Embodiment 4.

FIG. 79 shows an operation performed based on the new data transmissioncommand under the FMPK state 3a, according to Embodiment 4.

FIG. 80 shows an operation performed based on the new data commitcommand under the FMPK state 1a, according to Embodiment 4.

FIG. 81 shows an operation performed based on the new data commitcommand under the FMPK state 2a, according to Embodiment 4.

FIG. 82 shows an operation performed based on the new data commitcommand under the FMPK state 3a, according to Embodiment 4.

FIG. 83 shows a write process according to Embodiment 5.

FIG. 84 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 5.

FIG. 85 shows the transition write process performed upon the occurrenceof the MP fault in the mid-stage of parity media update, according toEmbodiment 5.

FIG. 86 shows the transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 5.

FIG. 87 shows a write process according to Embodiment 6.

FIG. 88 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 6.

FIG. 89 shows the transition write process performed upon the occurrenceof the MP fault in the mid-stage of parity media update, according toEmbodiment 6.

FIG. 90 shows the transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 6.

FIG. 91 shows a first process of a write process according to Embodiment7.

FIG. 92 shows a second process of the write process according toEmbodiment 7.

DESCRIPTION OF EMBODIMENTS

Several embodiments of the present invention are now describedhereinafter.

In the following description, various types of information are expressedby “*** table,” but the various types of information may be expressed bydata structures other than tables. In order to describe that the varioustypes of information are independent of the data structures, “*** table”can be referred to as “*** information.”

Furthermore, in the following description, each process is describedusing “program” as the subject of the sentence; however, the subject ofthe sentence describing each process may be “processor”, because aprogram is executed by a processor (e.g., a CPU (Central ProcessingUnit)), to perform a certain process by appropriately using a storageresource (e.g., memory) and/or a communication interface device (e.g., acommunication port). The process that is described using “program” asthe subject may be performed by a storage system, a controller containedin the storage system, an MPPK contained in the controller, which isdescribed hereinafter, or an MP (Microprocessor) inside the MPPK. Theprocessor may include a hardware circuit that performs part of or theentire process performed by the processor. The computer program may beinstalled from a program source into each computer. The program sourcemay be, for example, a program distribution server or a storage medium.

Embodiment 1 Configuration of Storage System

A configuration of a storage system is described hereinafter as anexample of the application of the present invention.

FIG. 1 shows a configuration of a storage system. The storage system 10has a controller 100, and a storage unit 200 coupled to the controller100. In the diagram, the controller 100 and the storage unit 200 arecoupled to each other by a BE-I/F (Back End Inter/Face) 141.

The storage unit 200 has a plurality of (or one) FMPKs (Flash MemoryPacKage) 144. A physical storage medium adopted in the storage unit 200is a memory drive (e.g., an SSD (Solid State Drive)) that has anonvolatile semiconductor memory (e.g., a flash memory). One or aplurality of RAID (Redundant Arrays of Inexpensive (or Independent)Disks) groups 145 are configured by the plurality of FMPKs 144. In thepresent embodiment, a RAID group of RAID level 5 is formed by thecontroller 100 using the plurality of FMPKs 144. Furthermore, in thepresent embodiment, the FMPKs included in a single RAID group arecoupled to different buses. In the case where the RAID group isconfigured from the plurality of FMPKs coupled to a single bus, if afault occurs in the bus, none of the FMPKs becomes accessible;therefore, the data cannot be recovered. However, the RAID group may beconfigured by the plurality of FMPKs coupled to the same bus.

One or a plurality of host computers 30 and a management computer 20 arecoupled to the controller 100. The controller 100 and the host computer30 are coupled to each other by a predetermined communication network 1(e.g., a SAN (Storage Area Network)). The controller 100 and themanagement computer 20 are coupled to each other by a predeterminedcommunication network 150 (including e.g., a switch or a LAN (Local AreaNetwork)).

The controller 100 is composed of various packages (PK) such as an FEPK(Front End Package) 110, an MPPK (Microprocessor Package) 120, a CMPK(Cache Memory Package) 130, and a BEPK (Back End Package) 140. In theexample shown in FIG. 1, a plurality of the various packages (PK) aremultiplexed, but at least one type of PK of the plurality of types ofPKs may exist in the singular. The FEPK 110, the MPPK 120, the CMPK(Cache Memory Package) 130, and the BEPK 140 are coupled to one anotherby the predetermined communication network (including e.g., a switch)150.

The FEPK 110 has one or more FE-IFs (Front End Inter/Faces) 111, atransfer circuit 112, and a buffer 113. The FE-I/F 111 is an interfacedevice communicating with a communication device that exists at a frontend of the host computer 30 or the like. For example, the FE-I/F 111receives an I/O request (a write request or a read request) from thehost computer 30, temporarily stores the received I/O request in thebuffer 113, and transfers the I/O request to the MPPK 120 via thetransfer circuit 112. The FEPK 110 may have a control device such as aCPU. The buffer 113 is, for example, a volatile semiconductor memory.The buffer 113 may also be a nonvolatile semiconductor memory.

The BEPK 140 has one or more BE-I/Fs 141, a transfer circuit 142, and abuffer 143. The BE-I/F 141 is an interface device communicating with theFMPKs 144. For example, the BE-I/F 141 reads data from the FMPKs 144 andtemporarily stores the data in the buffer 143. The transfer circuit 142sends to the CMPK 130 the data written from the FMPKs 144 to the buffer143. The transfer circuit 142 also writes the data read from the CMPK130, into the buffer 143. The BE-I/F 141 sends the data written to thebuffer 143 to the FMPKs 144. The BEPK 140 may have a control device suchas a CPU. The BEPK 140 may also be an interface such as a disk adapterbetween a control device and a storage device. The buffer 143 is, forexample, a volatile semiconductor memory. The buffer 143 may also be anonvolatile semiconductor memory.

The MPPK 120 has a plurality of (or one) microprocessors (“MP,”hereinafter) 121, and one or a plurality of LMs (Local Memories) 122coupled to the MPs 121 by an internal path 123. The MPs 120 process theI/O request sent from the FE-I/F 111. Each LM 122 stores a necessaryportion of management information stored in an SM (Shared Memory) 132 orstores a computer program executed by the MPs 121. In the systemconfiguration according to the present embodiment, the MPPK 120 iscoupled to the FEPK 110, the CMPK 130, and the BEPK 140 by internalnetworks thereof. Therefore, the MPPK 120 can control transfer of datawith the PKs (the MPPK 120, FEPK 110, CMPK 130, and BEPK 140), andstorage/deletion of data transmitted to the buffer 113 of the FEPK 110,the CM (Cache Memory) 131 and SM 132 of the CMPK 130, and the buffer 143of the BEPK 140.

The CMPK 130 has a CM 131 and the SM 132. The CM 131 and the SM 132 are,for example, volatile semiconductor memories. At least either the CM 131or the SM 132 may be a nonvolatile memory.

The CM 131 has a storage region for temporarily storing I/O target datafor the storage medium. The SM 132 has a storage region in which arestored various pieces of management information (various pieces ofinformation used in operations performed by the storage system) andcomputer programs.

The buffer 143 of the BEPK 140 stores data read from the CM 131 andtransmitted to the FMPK 144. Generally, a buffer has a smaller capacitythan a CM. The buffer keeps data related to one certain process (e.g.,an I/O process) until the completion of the process. In other words, thedata stored in the buffer is deleted once a series of processes arecompleted. On the other hand, data stored in the CM basically is notdeleted even after the completion of a certain I/O process and remainson the CM as long as the CM has enough capacity. Furthermore, the datais reused in another I/O process. Data related to an I/O process isstored in the CM; however, the data is deleted asynchronously with theI/O process. When deleting the data stored in the CM, for example, thedata may be deleted starting with the chronologically oldest data thathas been stored for the longest period of time, or with the data havingthe oldest last access time. Regions in the CM and the data stored inthe CM are used by the MPPK, FEPK and BEPK; therefore a great amount ofload is imposed on the CM.

At least one type of an FC (Fibre Channel), a SAS (Serial Attached SCSI)or a SATA (Serial ATA) may be the interfaces of these components.

The management computer 20 is, for example, a computer with a displaydevice and an input device. For instance, the management computer 20transmits a command for establishing various settings on the storagesystem, in response to an operation of an SVP (Service Processor) by anadministrator. The SVP updates the management information stored in theSM 132 and sets information in the SM 132, in response to a command fromthe administrator. The management information includes regioninformation indicating a region within the CM 131 for storing data, andprocess stage information indicating one of a plurality of states of thesystem during a write process.

FIG. 2 shows a configuration example of one of the FMPKs 144. The FMPK144 has communication interface devices, storage devices, and a controldevice coupled to the communication interface devices and the storagedevices. The communication interface devices are, for example, a port1441 coupled to the communication network, and a disk I/F 1446 coupledto FMs 1443. An FM controller 1447 includes the port 1441, a logicaloperation circuit 1442, a CPU 1444, a memory 1445, and the disk I/F1446.

The storage devices are, for example, the memory 1445 and the FMs (FlashMemories) 1443. The control device is, for example, the CPU 1444. Inaddition to such a processor as the CPU 1444, the control device mayinclude a dedicated hardware circuit that performs a predeterminedprocess (e.g., compression, expansion, encryption, or decryption). Thededicated hardware circuit is, for example, the logical operation (e.g.,XOR (exclusive or) operation) circuit 1442 that computes a parity or ahalfway parity. The logical operation circuit 1442 is referred to as“XOR circuit 1442” in the following description.

The FM 1443 is a nonvolatile semiconductor memory (typically a NAND-typeFM chip) into/from which data is written/read in units of pages or inwhich data is erased in units of blocks. The FM includes a plurality ofblocks, each of which includes a plurality of pages. When rewriting datastored in the FM 1443, data cannot be overwritten on a physical region(a physical page) in which the former data is stored. Therefore, whenthe FM controller 1447 receives data to be updated to data stored in acertain physical page, the received data is written to another physicalpage. In so doing, mappings of a logical page address and physical pageaddress are updated. Then, the FM controller 1447 disables data beforeupdate, to obtain disabled data, and manages the updated data as enableddata. A physical page in which the disabled data is stored is erased. Aphysical page in which the enabled data is stored is associated with alogical page, but the physical page in which the disabled data is storedis not associated with the logical page. In the FM 1443, in order torewrite the data stored in a certain physical region, an erasing process(“block erasing,” hereinafter) needs to be executed on the data in thephysical region, in units of blocks. The block subjected to the erasingprocess can be emptied so that data can be rewritten thereto. The FM1443 may not only be a flash memory but also be a WORM memory (e.g., aphase-change memory). The FM controller 1447 carries out a reclamationprocess. In the reclamation process, the FM controller 1447 copies theenabled data stored in a certain block (data associated with the logicalpage) to another block, disables the enabled data of the copy-sourceblock, and erases this block. The FM controller 1447 then erases thedata in units of blocks.

A pointer table that associates a logical page accessed from thecontroller 100 with a physical page inside the FM 1443 is stored in thememory 1445 of the FMPK 144. The memory 1445 may temporarily have storedtherein data obtained from the controller 100. The memory 1445 is, forexample, a volatile semiconductor memory. The memory 1445 may also be anonvolatile semiconductor memory.

The RAID group that uses the plurality of FMPKs 144 is described next.

The controller 100 creates a RAID group of RAID level 5 from theplurality of FMPKs 144 (see FIG. 1). The controller 100 allocatesconsecutive regions from address spaces of the created RAID group to aplurality of logical volumes (LU: Logical Units).

The controller 100 allocates stripe lines extending across the addressspaces on the plurality of FMPKs 144. The address spaces on theplurality of FMPKs 144 that configure the stripe lines include anaddress space having user data stored therein and one address spacehaving parity data stored therein. For example, the controller 100allocates an FMPK number to each of the plurality of FMPKs 144, andshifts the FMPK numbers allocated to the user data and the parity data,for each stripe line. The controller 100 writes information related toeach RAID group and the LUs into the LMs 122.

Hereinafter, of the plurality of FMPKs 144 allocated to the RAID group,the FMPK 144 that stores the user data indicated by a write command isreferred to as “data FMPK 144A”, and the FMPK 144 that stores the paritydata based on the user data is referred to as “parity FMPK 144P.”

The storage system 10 is capable of performing a read-modify-writeprocess in accordance with a write request from the host computer 30.The read-modify-write process is a write process for updating only theuser data stored in a logical region (block or page) of a single FMPK144 in a certain stripe line.

In the following description, user data before update in the logicalregion designated by the write request is referred to as “old userdata,” user data after update in the logical page as “new data,” paritydata before update based on the old user data as “old parity,” andparity data after update based on the new user data as “new parity.” Inthe following description and drawings, the old user data is referred toas “oD,” the new user data as “nD,” the old parity as “oP,” and the newparity as “nP.” In addition, an XOR operator is marked with “+.”

In the read-modify-write process, for example, an intermediate parity isgenerated by the XOR operation performed on the old data and the newdata, and the new parity is generated by the XOR operation performed onthe intermediate parity and the old parity. In the following descriptionand drawings, the intermediate parity is referred to as “mP.” In otherwords, the mP is computed from (oD+nD), and the nP is computed from(oP+mP).

Setting of parity calculation functions of the FMPK 144 is describednext.

In the following embodiments, the FMPK 144 having the logical operationcircuit 1442 performs parity calculation for generating intermediateparities and parities in accordance with instructions from thecontroller 100. The controller 100 (any one or more of the MPPK 120, theBEPK 140, the FEPK 110, and the CMPK 130) may have a logical operationfunction. In the case where both the FMPK 144 and the controller 100have logical operation functions, which one of the logical operationfunctions should be used to calculate the intermediate parities and/orparities may be determined based on a user operation.

In this case, the management computer 20 may display a menu screen forsetting the parity calculation functions of the FMPK 144. FIG. 3 showsthe menu screen. This menu screen G100 has an FMPK setting field G101, alogical volume setting field G104, a save button B10, and a cancelbutton B11.

The FMPK setting field G101 is an entry field for setting theavailability of an XOR function of the FMPK 144. The FMPK setting fieldG101 has a GUI, such as a radio button G102, for inputting an enablestate or a disable state of the XOR function of the FMPK 144.

The logical volume setting field G104 becomes enabled when the XORfunction of the FMPK 144 is set as enable through the FMPK setting fieldG101. The logical volume setting field G104 has a logical volume numberdisplay field G105 and an XOR function setting field G106. The logicalvolume number display field G105 displays a logical volume numbercreated by the FMPK 144. The XOR function setting field G106 is an entryfield for setting the availability of the XOR function of the FMPK 144with respect to the logical volume displayed on the logical volumenumber display field G105. The XOR function setting field G106 is a GUI,such as a radio button, for inputting an enable state or a disable stateof the XOR function of the logical volume.

The save button B10 is a button for saving the settings input to themenu screen G100 and then closing the menu screen G100. The cancelbutton B10 is a button for discarding the settings input to the menuscreen G100 and then closing the menu screen G100.

In the case where the XOR function of the FMPK 144 is set as enable fora certain logical volume, the XOR circuit 1442 of the FMPK 144 generatesthe intermediate parity or the new parity during the write process forthe logical volume. When the XOR function of the FMPK 144 is set asdisable for a certain logical volume, the controller 100 generates theintermediate parity or the new parity during the write process for thelogical volume.

In this manner, a user can set the availability of the XOR function ofthe FMPK 144 and the availability of the XOR function of the FMPK 144for each logical volume. According to the above description, the storageregions based on the RAID group are allocated beforehand to all of theregions of the logical volume. However, a logical volume according tothin provisioning (virtual volume) may be applied to the logical volume.Storage regions for storing data are not allocated beforehand to thevirtual volume; however, the storage regions are allocated to thevirtual volume in terms of a predetermined unit, in response to a writerequest with respect to the virtual volume. In the case where the writerequest is targeted to the regions of the virtual volume to which thestorage regions are allocated, the storage regions are not necessarilyallocated. The MPPK 120 of the controller 100 allocates the storageregions and manages the allocated or unallocated regions.

Write Process According to Embodiment 1

A normal write process is now described hereinafter.

Here is described a case where the storage system 10 performs theread-modify-write process based on a write command from the hostcomputer 30. The read-modify-write process updates data stored at leastin a single page within the RAID group created by the FMPKs 144.

In this embodiment, in addition to a normal write command and a normalread command, a new data transmission command, an intermediate parityreception command, an intermediate parity transmission command, and anew data commit command are defined as I/O commands sent from thecontroller 100 to the FMPK 144.

FIG. 4 shows a write process according to Embodiment 1. This diagram andthe subsequent sequence diagrams show operations by the host computer30, the controller 100, the data FMPK 144A, and the parity FMPK 144P.The operation targets in the upper sequence (operations prior to S2350)in this sequence diagram are the SM 132, the MP 121, the CM 131, thebuffer 113 of the FEPK 110, the I/F 111 of the FEPK 110, and the hostcomputer 30. The operation targets in the lower sequence (operationsafter S2350) in the sequence diagram are the SM 132, the MP 121, the CM131, the buffer 143 of the BEPK 140, the I/F 141 of the BEPK 140, theport 1441 of the data FMPK 144A, the XOR circuit 1442 of the data FMPK144A, storage media DFa and DFb of the data FMPK 144A, the port 1441 ofthe parity FMPK 144P, the XOR circuit 1442 of the parity FMPK 144P, andstorage media PFa and PFb of the parity FMPK 144P.

Here, the storage medium DFa of the data FMPK 144A represents the memory1445 of the FM 1443. The storage medium DFb represents a physical pageof the FM 1443. Furthermore, the storage medium DFa of the data FMPK144A represents the memory 1445 of the FM 1443. The storage medium DFbrepresents a physical page of the FM 1443. The storage medium PFa of theparity FMPK 144P represents the memory 1445 of the parity FM 1443. Thestorage medium PFb represents a physical page inside the parity FM 1443.

In this sequence diagram, the number of accesses to each of theoperation targets in the write process is shown below an operation(lifeline) of each operation target.

In the data FMPK 144A, the DFb is a physical page that stores the olduser data before the write process, and DFa is a physical page,different from the DFb, which stores the new user data after the writeprocess. In the parity FMPK 144P, the PFb is a physical page, differentfrom the PFa, which stores an old parity before the write process, andthe PFa is a physical page that stores the new parity after the writeprocess.

For the purpose of illustration, hereinafter a state of the storagesystem 10 in the write process is referred to as a “system state.” Somesystem states of the storage system 10 are defined hereinafter. As willbe described later, data loss upon the occurrence of a fault can beavoided by changing the process performed upon the occurrence of afault, in accordance with the system state.

First, the host computer 30 sends a write command for updating the olduser data to the new user data to the controller 100 of the storagesystem 10.

FIG. 5 shows an operation performed by the MP 121 upon reception of thewrite command, according to Embodiment 1. The MP 121 receives the writecommand from the host computer 30 (S2110). The MP 121 then secures aregion in the buffer 113 of the FEPK 110 to write the new user datathereto (S2120). The MP 121 then transmits a write preparationcompletion to the host computer 30 (S2130).

In the controller 100 shown in FIGS. 1 and 4, the I/F 111 of the FEPK110 writes the new data obtained from the host computer into a region inthe buffer 113, secured in S2120.

FIG. 6 shows an operation performed by the MP 121 after the execution ofwriting into the buffer 113 of the FEPK 110, according to Embodiment 1.Subsequently, the MP 121 is notified by the host computer 30 of thecompletion of writing into the buffer 113 (S2210). The MP 121 thensecures regions in the CMs 131 of two CMPKs 130 to write the new userdata thereto (S2220). The MP 121 then transmits to the FEPK 110 a writeinstruction for writing the new user data into the secured regions ofthe two CMs 131 (S2230).

In the controller 100 shown in FIGS. 1 and 4, the transfer circuit 112of the FEPK 110 duplicates the new user data stored in the buffer 113and writes the resultant data into the regions of the two CMs 131,secured in S2230.

FIG. 7 shows an operation performed by the MP 121 after the execution ofwriting new user data into the CMs 131, according to Embodiment 1.Subsequently, the MP 121 is notified by the FEPK 110 of the completionof writing into the two CMs 131 (S2310). The MP 121 then writes values(addresses on CM) indicating the regions of the two CMs 131, in whichthe new user data are stored, into region information items stored intwo SMs 132 corresponding to the two CMs 131 (S2320). The MP 121 thenwrites values indicating a pre-parity generation stage into processstage information items stored in the two SM 132 corresponding to theregions of the two CMs 131 (S2330). The MP 121 then registers thispre-parity generation stage in a pre-parity generation queue in the SM132 (S2340). Subsequently, the MP 121 instructs the FEPK 110 to releasethe buffer 113 in which the new user data is stored (S2345). The MP 121then notifies the host computer 30 of a normal end of the write command(S2350). MP 121 stores the region information items and process stepinformation items on the SM for each write process performed on the newuser data. When a fault occurs in an MP, other MPs are enabled to takeover a write process by referring to process step information items.

The system state at this moment is called “state 1.”

FIG. 8 shows an operation performed by the MP 121 after a write commandresponse is obtained, according to Embodiment 1. Subsequently, once theMP 121 detects that there is a registration in the pre-parity generationqueue (S2410), the MP 121 secures a region in the buffer 143 of the BEPK140 to write the new user data thereto (S2420). The MP 121 thentransmits to the BEPK 140 an instruction for reading the new user datafrom one of the CMs 131 (S2430).

In the controller 100 shown in FIG. 4, the transfer circuit 142 of theBEPK 140 reads the new user data from the CM 131 and writes the new userdata into the buffer 143.

FIG. 9 shows an operation performed by the MP 121 after the execution ofwriting into the buffer 143 of the BEPK 140, according to Embodiment 1.Subsequently, once the MP 121 is notified by the BEPK 140 of thecompletion of the reading (S2510), it transmits to the data FMPK 144A anew data transmission command for writing the new user data (S2530).This new data transmission command designates a logical page that storesa logical page of the old user data, and accompanies the new user data.

At this moment, the I/F 141 of the BEPK 140 reads the new user data fromthe buffer 143 and sends the new user data to the data FMPK 144A.

Next, in the data FMPK 144A shown in FIG. 4, the CPU 1444 receives thenew data transmission command and the new user data via the port 1441,writes the new user data into the DFa of the FM 1443, and notifies thecontroller 100 of a normal end of the new data transmission command.Here, in the FM 1443, the new user data and the old user data are storedand kept in a physical page associated with a certain logical pageaddress. The stored new user data and old user data are kept in thephysical page, at least until a new parity is generated based on thestored new user data and old data and then written to the physical page.

The system state at this moment is called “state 2.”

FIG. 10 shows an operation performed by the MP 121 after the normal endof the new data transmission command, according to Embodiment 1.Subsequently, once the MP 121 is notified by the data FMPK 144A of thenormal end of the new data transmission command (S2610), the MP 121secures the storage region of the buffer 143 of the BEPK 140 (S2620),and transmits to the data FMPK 144A an intermediate parity receptioncommand for causing the data FMPK 144A to generate an intermediateparity and acquiring the intermediate parity (S2630). This intermediateparity reception command designates the logical page that stores thelogical page of the old user data.

In the data FMPK 144A shown in FIG. 4, the CPU 1444 receives theintermediate parity reception command via the port 1441, reads the olduser data from the DFb, reads the new user data from the DFa, and sendsthe old user data and the new user data to the XOR circuit 1442. The XORcircuit 1442 calculates an intermediate parity from the old user dataand the new user data. The CPU 1444 notifies the BEPK 140 of a normalend of the intermediate parity reception command, through the port 1441,and sends the intermediate parity to the controller 100.

Next, in the controller 100 shown in FIG. 4, the I/F 141 of the BEPK 140writes the intermediate parity received from the data FMPK 144A, intothe storage region of the buffer 143, secured in S2620.

FIG. 11 shows an operation performed by the MP 121 after the normal endof the intermediate parity reception command, according to Embodiment 1.Once the MP 121 is notified by the data FMPK 144A of the normal end ofthe intermediate parity reception command (S3110), the MP 121 sends tothe parity FMPK 144P an intermediate parity transmission command forgenerating and writing a new parity from the intermediate parity(S3120). This intermediate parity transmission command designates thelogical page that stores the logical page of the old parity, andaccompanies the intermediate parity.

At this moment, the I/F 141 of the BEPK 140 reads the intermediateparity from the buffer 143 and sends the intermediate parity to theparity FMPK 144P. Here, the MP 121 stores the intermediate parity, whichis read from the data FMPK 144A, into the buffer 143 of the BEPK 140,and then transfers the intermediate parity to the parity FMPK withoutstoring the intermediate parity in the CM 131. Because the CM 131 is notused when transferring the intermediate parity, the load imposed on theCM 131 can be reduced, improving the performance of the storage system.Moreover, because each FMPK 144 is coupled to a position in the vicinityof the buffer 143, the intermediate parity can be transferredefficiently.

Next, in the parity FMPK 144P shown in FIG. 4, the CPU 1444 receives theintermediate parity transmission command and the intermediate parity viathe port 1441, reads the old parity from the PFb, and sends the oldparity and the intermediate parity to the XOR circuit 1442. The XORcircuit 1442 calculates a new parity from the old parity and the newparity. The CPU 1444 writes the new parity into the PFa and notifies thecontroller 100 of a normal end of the intermediate parity transmissioncommand.

The system state at this moment is called “state 3.”

FIG. 12 shows an operation performed by the MP 121 after the normal endof the intermediate parity transmission command, according toEmbodiment 1. Subsequently, once the MP 121 is notified by the parityFMPK 144P of the normal end of the intermediate parity transmissioncommand (S3210), the MP 121 writes values indicating a post-paritygeneration stage into the process stage information items stored in theabovementioned two SMs 132 (S3220). The system state at this moment iscalled “state 4.” Next, the MP 121 instructs the BEPK 140 to release thebuffer area in which the intermediate parity is stored (S3225). The MP121 then sends a new data commit command to the data FMPK 144A (S3230).The new data commit command designates the logical page that stores thelogical page of the old user data.

Next, in the data FMPK 144A shown in FIG. 4, the CPU 1444 receives thenew data commit command via the port 1441, determines the new user dataas the user data after update, and notifies the controller 100 of anormal end of the new data commit command. As a result, the new userdata can be accessed based on the normal write command and the normalread command sent from the controller 100.

The system state at this moment is called “state 5.”

FIG. 13 shows an operation performed by the MP 121 after the normal endof the new data commit command transmitted to the data FMPK 144A,according to Embodiment 1. Once the MP 121 is notified by the data FMPK144A of the normal end of the new data commit command (S3310), the MP121 sends a new data determination to the parity FMPK 144P (S3320). Thisnew data commit command designates the logical page that stores the oldparity. As a result, the new user data can be accessed based on thenormal write command and the normal read command sent from thecontroller 100. The transmission of the new data commit command to thedata FMPK 144A and the transmission of the new data commit command tothe parity FMPK 144P may occur in reverse order.

Next, in the parity FMPK 144P shown in FIG. 4, the CPU 1444 receives thenew data commit command via the port 1441, determines the new parity asa parity after update, and notifies the controller 100 of a normal endof the new data commit command.

The system state at this moment is called “state 6.”

FIG. 14 shows an operation performed by the MP 121 after the normal endof the new data commit command transmitted to the parity FMPK 144P,according to Embodiment 1. Once the MP 121 is notified by the parityFMPK 144P of the normal end of the new data commit command (S3410), theMP 121 clears the regions of the two SMs 132 in which the process stageinformation items are stored (S3420), and ends the write process.

The system state at this moment is called “state 7.”

The above is the write process. The number of accesses to CM isindicated in parentheses below.

In this write process, the new user data from the host computer 30 isduplicated and written (twice) into the CM 131 of the CMPK 130 and isread from the other CM 131 and then sent from the CM 131 to the buffer143 of the BEPK 140. The new user data from the CM 131 is written to thebuffer 143 and sent from the buffer 143 to the data FMPK 144A. Theintermediate parity from the data FMPK 144A is written to the buffer 143and sent from the buffer 143 to the parity FMPK 144P. Because of this,the number of accesses to the CM 131 become three times in a singlewrite process, hence the number of accesses to the CM 131 can bereduced.

As described above, the FMPK 144 executes the parity calculation and thecontroller 100 sends the intermediate parity from the buffer 143 to theparity FMPK 144P without writing the intermediate parity received fromthe data FMPK 144A into the CM 131. As a result, the load imposed on theMP and the CM in the storage controller can be reduced, improving thewrite process performance of the storage system.

For a comparison purpose, now is described a case where the controller100 performs the parity calculation on the RAID 5 using the CM 131 in aconventional write process. In this case, the controller 100 duplicatesthe new user data obtained from the host computer, writes the resultantdata into the CM (twice), acquires the old user data from the data FMPK144A, writes the old user data into the CM 131 (once), acquires the oldparity from the parity FMPK 144P, and writes the old parity into the CM131 (once). Furthermore, the controller 100 reads the old user data, thenew user data, and the old parity stored in the CM 131 (three times) tocalculate a new parity, duplicates the new parity and writes theresultant parities into two CMs 131 (twice), reads the new user datastored in the CM 131 (once), writes the new user data into the data FMPK144A, reads the new parities stored in the CMs 131 (once), and writesthe new parities into the parity FMPK 144P. In this case, the number ofaccesses to the CM 131 in a single write process is eleven.

In this embodiment, the intermediate parity can be transferredefficiently by using the buffer 143 of the BEPK 140 located in thevicinity of the FMPK 144.

Furthermore, the RAID 5 is configured by the plurality of FMPKs 144coupled to the different buses, in order to maintain a redundantconfiguration upon system fault. Allowing the plurality of FMPKs 144 toshare the buffer of the BEPK 140 can maintain the redundantconfiguration and transfer the intermediate parity using the buffer.According to this embodiment, the reliability of the storage system 10can be improved by storing the new user data in two CMPKs 130 andstoring the process stage information items corresponding to the newuser data into the SMs 132.

The CM 131 having the new user data stored therein and the SM 132 havingthe process stage information corresponding to the new user data storedtherein may be provided in the packages different from each other.Furthermore, the pointer table of the FMPK 144 is stored in the memory1445 but may be stored in the FM 1443.

Transition Write Process according to Embodiment 1

A transition write process that is performed upon an occurrence of an MPfault is described hereinafter.

The takeover write process is a process that occurs when a fault occursin the MP 121 during the write process. In this case, the other MPs 121free of faults perform the transition write process that takes over thewrite process. During the write process, the MPs 121 free of faults canrecognize the process stage information items, since the process stageinformation items are stored in the two SMs 132, and perform anappropriate transition write process in accordance with the processstage information items. If the process stage information items arelost, data loss occurs. Data loss is a situation where write data of thehost computer are lost and therefore cannot be recovered. Data loss isnot a favorable condition for the storage system. Therefore, the processstage information items are duplicated and stored. Moreover, atransition write process described hereinafter is executed in order toavoid data loss caused upon the occurrence of an MP fault.

The transition write process is now described. FIG. 15 shows anoperation performed by the MP 121 upon the occurrence of the MP fault,according to Embodiment 1. First, the MP 121 of the MPPK 120 free offaults detects the occurrence of a fault in the other MPPK 120 (S3610).The MP 121 then selects one of the SMs 132 that is not searched fromamong a plurality of SMs 132 (S3620), searches this SM 132, anddetermines whether or not the pre-parity generation stage of the processstage information items is detected from the searched SM 132 (S3630).

When the pre-parity generation stage is detected (S3630, YES), the MP121 registers the pre-parity generation stage in the pre-paritygeneration queue of the SM 132 on the basis of the region informationstored in the SM 132 (S3640), and advances the process to S3670.

On the other hand, when the pre-parity generation stage is not detected(SS3630, NO), the MP 121 determines whether or not a post-paritygeneration stage of the process stage information item is detected fromthe searched SM 132 (S3650).

When the post-parity generation stage is detected (S3650, YES), the MP121 registers this post-parity generation stage in the post-paritygeneration queue stored in the SM 132 based on the region informationstored in the SM 132 (S3660), and advances the process to S3670.

When the post-parity generation stage is not detected (S3650, NO), theMP 121 ends this process flow.

Subsequent to S3640 and S3660, the MP 121 determines whether searchingfor all SMs 132 is completed or not (S3670). When searching for all SMs132 is not completed (S3670, NO), the MP 121 returns the process toS3620. When searching for all SMs 132 is completed (S3670, YES), the MP121 ends this process flow.

The operations that are performed by the MP 121 when there is aregistration in the pre-parity generation queue are the same as S2410 toS2430 described above. In other words, the MP 121 takes over the processat the stage where the new user data stored in the CM 131 is transferredto the BEPK 140.

FIG. 16 shows an operation performed by the MP 121 in the case wherethere is a registration in the post-parity generation queue, accordingto Embodiment 1. Once the MP 121 detects that there is a registration inthe post-parity generation queue (S3710), the MP 121 sends the new datacommit command to the data FMPK 144A (S3720). Specifically, when thereis a registration in the post-parity generation queue of any of the SMs132, the MP 121 takes over the write process, from the point where thenew data commit command is transmitted to the data FMPK 144A, as withthe case of the normal write process.

In this manner, the MP 121 free of faults can take over the writeprocess from the MP 121 having a fault, depending on the type of theprocess stage information item stored in the SM 132.

Specific Examples of Transition Write Process According to Embodiment 1

Several specific examples of the transition write process performed uponthe occurrence of the MP fault are now described.

First Specific Example of Transition Write Process According toEmbodiment 1

Here is described the transition write process that is performed uponthe occurrence of the MP fault in the pre-parity generation stage.

FIG. 17 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 1. The key components of the operations shown in thissequence diagram are the same as those shown in the sequence diagramsrelated to the normal write process.

Once the MP 121 free of faults acknowledges that the process stageinformation items indicate the pre-parity generation stage, the MP 121free of faults send the new data transmission command to the data FMPK144A, as in the normal write process described above (S2530).Consequently, the data FMPK 144A writes the new user data into the DFa(memory 1445).

Next, in the controller 100, the MP 121 sends the intermediate parityreception command to the data FMPK 144A, as in the normal write process(S2630). Accordingly, the data FMPK 144A calculates the intermediateparity and sends the intermediate parity to the controller 100.Consequently, the BEPK 140 writes the intermediate parity into thebuffer 143.

In the controller 100, the MP 121 then sends the intermediate paritytransmission command to the parity FMPK 144P, as in the normal writeprocess (S3120). Consequently, the parity FMPK 144P calculates the newparity and writes the new parity into the PFa (memory 1445).

Subsequently, in the controller 100, the MP 121 sends the new datacommit command to the data FMPK 144A, as in the normal write process(S3230). Consequently, the data FMPK 144A determines the new user dataas the user data after update.

In the controller 100, the MP 121 then sends the new data commit commandto the parity FMPK 144P, as in the normal write process (S3320).Consequently, the parity FMPK 144P determines the new parity as theparity after update.

The above is the transition write process.

Because the process stages are recorded in the SMs 132, another MP 121free of faults can take over the write process even upon the occurrenceof a fault in a certain MP 121. When the process stage information itemsindicate the pre-parity generation stage at the time of the occurrenceof the MP fault, the other MP 121 free of faults takes over the writeprocess at the stage where the new user data is transferred from the CM131 to the BEPK 140.

Second Specific Example of Transition Write Process According toEmbodiment 1

Here is described the transition write process that is performed uponthe occurrence of the MP fault in the post-parity generation stage.

FIG. 18 shows a transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 1. The operation targets of the operations shown in thissequence diagram are the same as those shown in the sequence diagramsrelated to the normal write process. Once the MP 121 free of faultsacknowledges that the process stage information items indicate thepost-parity generation stage, the MP 121 free of faults sends the newdata commit command to the data FMPK 144A, as in the normal writeprocess (S3230). Consequently, the data FMPK 144A determines the newuser data as the user data after update.

In the controller 100, the MP 121 then sends the new data commit commandalso to the parity FMPK 144P, as in the normal write process (S3320).Consequently, the parity FMPK 144P determines the new parity as theparity after update.

The above is the transition write process.

As described above, recording the process stage information items in theSMs 132 can allow the other MP to take over the write process even uponthe occurrence of a fault in a certain MP. When the process stageinformation items indicate the post-parity generation stage at the timeof the occurrence of the MP fault, the other MP 121 free of faults takesover the write process at the stage where the new user data stored inthe data FMPK 144A is determined. When the process stage informationitems indicate the post-parity generation stage, it is not necessary tore-transfer the user data from the CM 131, because the new user dataexists in the FMPK 144A. In other words, this transition write processdoes not cause additional access to the CM 131.

FMPK State in Write Process According to Embodiment 1

Hereinafter, the state of the parity FMPK 144P during the write processis referred to as “FMPK state,” and “FMPK state 1” and “FMPK state 2”are described hereinbelow. FIG. 19 shows the FMPK state 1, according toEmbodiment 1. FIG. 20 shows the FMPK state 2, according to Embodiment 1.

In the following description of the operations by the FMPK 144, the olduser data stored in the data FMPK 144A and the old parity stored in theparity FMPK 144P are referred to as “old data.” The new user data storedin the data FMPK 144A and the new parity stored in the parity FMPK 144Pare referred to as “new data.” In other words, the operations by theFMPK 144 described hereinafter can be applied to the operations by thedata FMPK 144A and the operations by the parity FMPK 144P. Furthermore,“additional data” indicates the new user data that is re-transmittedfrom the controller 100 to the FMPK 144 by the transition write process.The operations performed mainly by the CPU 1444 of the FMPK 144 aredescribed using the FMPK 144.

A pointer table 1448 that associates a logical page accessed from thecontroller 100 with some physical pages inside the FM 1443 is stored inthe memory 1445 of each FMPK 144. The pointer table 1448 includescorrespondence relationships of the physical pages to all logical pageswithin the FMPK 144. In the following description, of the logical pageswithin each FMPK 144, the logical page designated by a command sent fromthe controller 100 to the FMPK 144 is referred to as “target logicalpage.” Of the entries in the pointer table 1448 shown in the memory1445, the entry for the target logical page is referred to as “targetentry 1449.”

The target entry 1449 has a field for a logical page address, which is alogical address (e.g., LBA: Logical Block Address) designating thetarget logical page, a field for an old physical page address, which isa physical address designating an old physical page, and a field for anew physical page address, which is a physical page different from theabovementioned physical page and designating a new physical page as acandidate for an old physical page. In the diagram and the followingdescription, in the target entry 1449, the logical page address iscalled “LA,” the old physical page address is called “oPA,” and the newphysical page address is called “nPA.” In the diagram and the followingdescription, the value of the logical page address is described as “LBAxxxx,” and the values of the old physical page address and the newphysical page address are described as “p0,” “p1,” “p2,” etc.

In the diagrams, an arrow directed from the physical page address storedin the target entry 1449 to the inside of the FM 1443 represents apointer, indicating that this physical page address indicates thephysical page pointed by the arrow. When the arrow is in the form of adashed line, it means that the pointer of the arrow is deleted.

In the case where the FMPK 144 receives from the controller 100 a normalwrite command and a normal read command for the target physical page,the FMPK 144 associates the target logical page with the old physicalpage based on the target entry 1449 of the pointer table, to access theold physical page. In other words, the normal access from the controller100 is performed only on the old physical page.

The target entry 1449 may have stored therein a logical page numberindicating the logical page, in place of the logical page address. Thetarget entry 1449 may have stored therein a physical page numberindicating the old physical page, in place of the physical page address.The target entry 1449 may have stored therein a physical page numberindicating the new physical page, in place of the new physical pageaddress. The pointer table is managed and updated by the CPU 1444.

In the following description, when the FMPK 144 registers the value of aphysical address for storing data, into the old physical page address orthe new physical page address of the target entry 1449, this operationis called “pointer connection” for the data. In addition, when the FMPK144 changes the value registered in the old physical page address or thenew physical page address of the target entry 1449 to the value of aphysical address of a physical page having other data, this operation iscalled “pointer replacement” for the data. When the FMPK 144 deletes thevalue registered in the old physical page address or the new physicalpage address of the target entry 1449, this operation is called “pointerdeletion” for the data. These operations mean that the CPU 1444 updatesthe target entry 1449 of the pointer table.

In “FMPK state 1,” the old data is stored in the old physical page. Thelogical page address and the old physical page address are stored in thetarget entry 1449. In the “FMPK state 2,” the old data is stored in theold physical page, and the new data is stored in the new physical page.The logical page address, the old physical page address, and the newphysical page address are stored in the target entry 1449. In “FMPKstate 1,” the old data is the enabled data. In “FMPK state 2,” the newdata and the old data are the enabled data. In the case where thereclamation process is executed in “FMPK state 2,” since the new dataand the old data are the enabled data, the new data and the old data arecopied from the blocks that respectively store the new data and the olddata, to other empty blocks. The FM controller 1447 may perform controlin a manner that the blocks that include the new data and/or the olddata obtained during the parity calculation are not reclaimed. Eitherway, the FM controller 1447 does not erase the old data until receivingthe new data commit command. In this manner, the intermediate parity canbe generated in a process performed upon the occurrence of a fault, theprocess being described hereinafter. Next is described the target entryof the pointer table. The FM controller 1447 can execute the paritycalculation process and the read/write process in parallel on aplurality of entries (logical pages).

Operations by FMPK 144 Based on Command

An operation by the FMPK 144 based on each command is describedhereinafter.

FIG. 21 shows an operation performed based on the new data transmissioncommand under the FMPK state 1, according to Embodiment 1. Thisoperation corresponds to S2530 described above. In the FMPK 144, the olddata is stored in the old physical page. In the target entry 1449, theold physical page address indicates the old physical page. First, theBEPK 140 sends the new data transmission command designating the targetlogical page and accompanying new data to the FMPK 144 (S5110). The FMPK144 stores the new data temporarily in the memory 1445 and afterwardwrites the new data into the new physical page of the FM 1443 (S5120).The FMPK 144 then performs the pointer connection on the new data bydesignating the new physical page for the new physical page address ofthe target entry 1449 (S5130). Subsequently, the FMPK 144 sends a normalend response to the controller 100 (S5140). This operation allows thesystem state to transit from the state 1 to the state 2. With this newdata transmission command, the correspondence relationship between thelogical page address and the old physical page address can be maintainedeven after writing the new data, without having the old data disabled.When the FM controller 1447 described hereinafter receives the new datacommit command, the correspondence relationship between the logical pageaddress and the old physical page address is canceled. Moreover, withthe new data transmission command, the new data can be written to thephysical page of the physical page of the FM prior to the generation ofthe intermediate parity. The old user data is kept in the parity FMPK144P until the new parity is written to the physical storage region.Accordingly, even upon the occurrence of a fault, the intermediateparity can be generated using the old user data. The normal writeprocess, on the other hand, is described with reference to FIG. 31.

FIG. 22 shows an operation performed based on the new data transmissioncommand under the FMPK state 2, according to Embodiment 1. In the FMPK144, the old data is stored in the old physical page and the new data isstored in the new physical page. In the target entry 1449, the oldphysical page address indicates the old physical page, and the newphysical page address indicates the new physical page. First, thecontroller 100 sends the new data transmission command designating thetarget logical page and accompanying additional data to the FMPK 144(S5210). The FMPK 144 stores the additional data temporarily in thememory 1445 and afterward writes the additional data into an additionalphysical page, which is a physical page different from the old physicalpage and the new physical page of the FM 1443 (S5220). The FMPK 144 thenperforms the pointer replacement for replacing the new data with theadditional data, by designating the additional physical page for the newphysical page address of the target entry 1449 (S5230). Subsequently,the FMPK 144 sends a normal end response to the controller 100 (S5240).In this process, the new data stored in the FM is not taken as the olddata. Since the stage occurs prior to the generation of the new parity,the old data obtained when the old parity was generated is maintained asthe old data. When processing the new data transmission command, theFMPK state does not transit from the FMPK state 2. In other words, whenprocessing the new data transmission command in the FMPK state 1, theFMPK state transits to the FMPK state 2. When processing the new datatransmission command in the FMPK state 2, the FMPK state remains as theFMPK state 2. This means that the transition of the state of the FMPKoccurs due to the new data transmission command, regardless of the stateof the FMPK. The normal write process, on the other hand, is describedwith reference to FIG. 32.

FIG. 23 shows an operation performed based on the intermediate parityreception command under the FMPK state 1, according to Embodiment 1.First, the controller 100 sends the intermediate parity receptioncommand to the FMPK 144 (S5310). This intermediate parity receptioncommand designates the target logical page. Subsequently, the FMPK 144sends an abnormal end response to the controller 100 (S5320).

FIG. 24 shows an operation performed based on the intermediate parityreception command under the FMPK state 2, according to Embodiment 1. Inthe FMPK 144, the old data is stored in the old physical page, and thenew data in the new physical page. In the target entry 1449, the oldphysical page address indicates the old physical page, and the newphysical page address indicates the new physical page. In other words,the old physical page and the new physical page are mapped to thelogical page address. First, the controller 100 sends the intermediateparity reception command to the FMPK 144 (S5410). This intermediateparity reception command designates the target logical page. The FMPK144 then reads the old data and the new data indicated respectively bythe old physical page address and the new physical page address storedin the target entry 1449, and generates an intermediate parity using theXOR circuit 1442 (S5420). In the FMPK 144, mapping to the old data ismaintained based on the new data transmission command from thecontroller 100. Accordingly, the FM controller can specify the new userdata and the old user data for a certain logical page address.Subsequently, the FMPK 144 sends a response regarding the intermediateparity to the controller 100 (S5430). In addition, as shown in FIG. 22,the same process is carried out even when the additional data is storedin the FM. In other words, the FM controller generates the intermediateparity from the additional user data and the old user data. In the FMPK144, the intermediate parity generation process is executed a number oftimes on the other user data, in parallel with the normal read/writeprocess, and the memory 1445 is used in these processes as well.Therefore, maintaining the written new user data in the memory 1445 andwriting the intermediate parity to the FM after the generation thereofincreases the period of time in which the new user data is stored in thememory. This can deteriorate the performance of the read/write process.In the present embodiment, the FM controller reads the new user data andthe old user data to generate the intermediate parity after writing thenew data into the FM and upon reception of the intermediate parityreception command. Thus, the period of time in which the new user dataand the old user data are stored in the memory 1445 of the FMPK 144 canbe shortened when the intermediate parity is generated. As a result, theregion in the memory that can be used in the read/write process can beincreased, improving the process performance of the FMPK 144.

FIG. 25 shows an operation performed based on the intermediate paritytransmission command under the FMPK state 1, according to Embodiment 1.In the FMPK 144, the old parity is stored in the old physical page. Inthe target entry 1449, the old physical page address indicates the oldphysical page. First, the BEPK 140 sends to the FMPK 144 theintermediate parity transmission command designating the target logicalpage and related to the intermediate parity (S5510). Then, the FMPK 144temporarily stores the intermediate parity in the memory 1445, reads theold parity from the old physical page indicated by the old physical pageaddress of the target entry 1449, temporarily stores the old parity inthe memory 1445, generates a new parity from the intermediate parity andthe old parity by using the XOR circuit 1442, and writes the new parityto the new physical page (S5520). The FMPK 144 then performs the pointerconnection on the new parity by designating the new physical page forthe new physical page address of the target entry 1449 (S5530).Subsequently, the FMPK 144 sends a normal end response to the controller100 (S5540).

FIG. 26 shows an operation performed based on the intermediate paritytransmission command under the FMPK state 2, according to Embodiment 1.In the FMPK 144, the old data is stored in the old physical page and thenew data is stored in the new physical page. In the target entry 1449,the old physical page address indicates the old physical page, and thenew physical page address indicates the new physical page. First, thecontroller 100 sends the intermediate parity transmission commanddesignating the target logical page and accompanying the intermediateparity to the FMPK 144 (S5610). The FMPK 144 then reads the old datafrom the old physical page indicated by the old physical page addressstored in the target entry 1449, generates additional data from theintermediate parity and the old data using the XOR circuit 1442, andwrites the additional data into the additional physical page differentfrom the old physical page and the new physical page (S5620). The FMPK144 then performs the pointer replacement for replacing the new datawith the additional data, by designating the additional physical pagefor the new physical page address of the target entry 1449 (S5630).Subsequently, the FMPK 144 sends a normal end response to the controller100 (S5640). In this manner, even in the FMPK state 1 or the FMPK state2, the additional parity (same as the new parity) can be generated fromthe old parity and the intermediate parity when the FM controllerreceives the intermediate parity transmission command.

FIG. 27 shows an operation performed based on the new data commitcommand under the FMPK state 1, according to Embodiment 1. When thisprocess is performed by the data FMPK 144A, the new data is determined.When the process is performed by the parity FMPK 144P, the new parity isdetermined. In the FMPK 144, the old data is stored in the old physicalpage. In the target entry 1449, the old physical page address indicatesthe old physical page. First, the controller 100 sends the new datacommit command to the FMPK 144 (S5710). This new data commit commanddesignates the target logical page. Subsequently, the FMPK 144 sends anormal end response to the controller 100 (S5720). In other words,because the new data is already determined, the FMPK state 1 isrecognized as a normal state. This process is executed in order toconfirm the FMPK state, when a system fault occurs after the new dataand the new parity are determined and before the process stageinformation items in the SMs 132 are cleared.

FIG. 28 shows an operation performed based on the new data commitcommand under the FMPK state 2, according to Embodiment 1. When thisprocess is performed by the data FMPK 144A, the new data is determined.When the process is performed by the parity FMPK 144P, the new parity isdetermined. As a result of this process, the state of the FMPK 144transits from the FMPK state 2 to the FMPK state 1. In the FMPK 144, theold data is stored in the old physical page and the new data is storedin the new physical page. In the target entry 1449, the old physicalpage address indicates the old physical page, and the new physical pageaddress indicates the new physical page. First, the controller 100 sendsthe new data commit command to the FMPK 144 (S5810). This new datacommit command designates the target logical page. The FMPK 144 thenperforms the pointer replacement for replacing the old data with the newdata, by designating the new physical page for the old physical pageaddress of the target entry 1449, and performs the pointer deletion onthe new data by deleting the new physical page from the new physicalpage address of the target entry 1449 (S5820). Subsequently, the FMPK144 sends a normal end response to the controller 100 (S5830). Afterthese steps, the FM controller responds with new data when receiving aread request. In this way, in both FMPK state 1 and FMPK state 2, theestablishment of the FMPK state 1 is ensured when the new data commitcommand is received

FIG. 29 shows an operation performed based on the normal read commandunder the FMPK state 1, according to Embodiment 1. First, the controller100 sends the normal read command to the FMPK 144 (S4310). This normalread command designates the target logical page. The FMPK 144 then readsthe old data indicated by the old physical page address of the targetentry 1449, and sends a response regarding the old data to thecontroller 100 (S4320).

FIG. 30 shows an operation performed based on the normal read commandunder the FMPK state 2, according to Embodiment 1. In the FMPK 144, theold data is stored in the old physical page, and the new data in the newphysical page. In the state 2, both the old physical page and the newphysical page are mapped to a certain LBA. In other words, for thestorage system, this state is where writing of the new data is notcompleted. First, the controller 100 sends the normal read command tothe FMPK 144 (S4410). This normal read command designates the targetlogical page. The FMPK 144 then reads the old data indicated by the oldphysical page address of the target entry 1449, and sends a responseregarding the old data to the controller 100 (S4420).

FIG. 31 shows an operation performed based on the normal write commandunder the FMPK state 1, according to Embodiment 1. In the FMPK 144, theold data is stored in the old physical page. In the target entry 1449,the old physical page address indicates the old physical page. First,the controller 100 sends the normal write command designating the targetlogical page and accompanying new data to the FMPK 144 (S4110). The FMPK144 then writes the new data into the new physical page stored in the FM1443 (S4120). The FMPK 144 then performs the pointer replacement forreplacing the old data with the new data, by designating the newphysical page for the old physical page address of the target entry 1449(S4130). Subsequently, the FMPK 144 sends a normal end response to thecontroller 100 (S4140). This operation does not allow the FMPK state totransit from the FMPK state 1.

FIG. 32 shows an operation performed based on the normal write commandunder the FMPK state 2, according to Embodiment 1. In the FMPK 144, theold data is stored in the old physical page and the new data is storedin the new physical page. In the target entry 1449, the old physicalpage address indicates the old physical page, and the new physical pageaddress indicates the new physical page. First, the controller 100 sendsthe normal write command designating the target logical page andaccompanying additional data to the FMPK 144 (S4210). The FMPK 144 thenwrites the additional data into the additional physical page, which is aphysical page different from the old physical page and the new physicalpage stored in the FM 1443 (S4220). The FMPK 144 then performs thepointer replacement on the old data by designating the additionalphysical page for the old physical page address of the target entry 1449(S4230). Subsequently, the FMPK 144 performs the pointer deletion on thenew data by deleting the new physical page from the new physical pageaddress of the target entry 1449 (S4240). The FMPK 144 then sends anormal end response to the controller 100 (S4250). This operation allowsthe system state to transit from the FMPK state 2 to the FMPK state 1.

Transitions of System State

FIG. 33 shows the each process according to Embodiment 1 and transitionsof the state of the system caused due to the occurrence of a systemfault. The states of the system adopted in this embodiment are, inaddition to the system states 1 to 7 described above, a system state a,system state b, system state c, system state e, system state f, systemstate A, system state B, system state C, system state D, system state E,system state F, system state G, and system state I, each of whichindicates a state of the system upon the occurrence of a fault. Thenumbers of the drawings describing the corresponding processes by theFMPK are shown in parentheses. In the drawing, the terms “pre-paritygeneration stage” and “post-parity generation stage” indicate thecontents of the process stage information items stored in the SM 132.The term “clear SM” means that the new data and the new parity aredetermined and that the process stage information items related to theFMPK are deleted from the SM 132. In the system states 1 to 3, thecorrespondence relationship between the logical page and the physicalpage in which the old user data is stored is kept in the data FMPK 144A.In the system states 1 to 3, the correspondence relationship between thelogical page and the physical page in which the old parity is stored iskept in the parity FMPK 144P. Therefore, when faults occur in the systemstates 1 to 3, the intermediate parity can be generated by allowing thecontroller 100 to transmit the new user data to the data FMPK 144A, andthe new parity can be generated from the intermediate parity and the oldparity. In the system states 4 to 6, the correspondence relationshipbetween the logical page and the physical page in which the new userdata is stored is kept in the data FMPK 144A. In the system states 4 to6, the correspondence relationship between the logical page and thephysical page in which the new parity is stored is kept in the parityFMPK 144P. Therefore, when faults occur in the system states 4 to 6, thenew user data and the new parity can be determined by allowing thecontroller 100 to transmit the new data commit command to the data FMPK144A and the parity FMPK 144P. As described above, the process stageinformation item stored in the SM 132 has two stages: “pre-paritygeneration stage” and “post-parity generation stage.” For this reason,data loss that is caused upon the occurrence of a fault can be avoided,and the load imposed to manage the process stage information item can bereduced. Managing the process stage information item in detail increasesthe number of accesses to the SMs 132 for recording the process stageinformation item therein and increases the load caused as a result ofthe accesses made to the SMs 132.

First, a Normal Transition of the System State is Described.

FIG. 34 shows an arrangement of data in the system state 1, according toEmbodiment 1. In the following description, two of the FEPKs 110 of thecontroller 100 are referred to as “FEPK 110A” and “FEPK 110B,”respectively. Two of the MPPKs 120 of the controller 100 are referred toas “MPPK 120A” and “MPPK 120B,” respectively. Two of the CMPKs 130 ofthe controller 100 are referred to as “CMPK 130A” and “CMPK 130B,”respectively. Two of the BEPKs 140 of the controller 100 are referred toas “BEPK 140A” and “BEPK 140B,” respectively. Of the plurality of FMPKs144 configuring the RAID groups, the FMPKs 144 other than the data FMPK144A and the parity FMPK 144P are referred to as “other data FMPKs144E.” In addition, in the diagram and the following description, theold user data, which is the user data obtained before the update by thewrite process, is referred to as “oDi,” the new user data, which is theuser data after the update, is referred to as “nDi,” other user data,which is the user data stored in the other data FMPKs 144E within thesame stripe as the oDi, is referred to as “oDx.” Furthermore, theintermediate parity is referred to as “mP,” the old parity as “oP,” andthe new parity as “nP.” In the drawings and the following description,the MP 121 of the MPPK 120A in the write process is referred to as “MPin process.”

The system state 1 occurs before the controller 100 transmits the newdata transmission command. The CM 131 of the CMPK 130A and the CM 131 ofthe CMPK 130B have the new user data stored therein. The SM 132 of theCMPK 130A and the SM 132 of the CMPK 130B show the pre-parity generationstages. The data FMPK 144A has the old user data stored therein. Theparity FMPK 144P has the old parity stored therein. The other FMPKs 144Ehave other user data stored therein. The old physical page address ofthe target entry 1449 of the data FMPK 144A indicates the old user data.The old physical page address of the target entry 1449 of the parityFMPK 144P indicates the old parity.

In the state 1, the controller 100 sends the new data transmissioncommand to the data FMPK 144A. As a result, the system state transits tothe state 2.

FIG. 35 shows an arrangement of data in the system state 2, according toEmbodiment 1. This state occurs after the completion of the new datatransmission command by the controller 100. The new data transmissioncommand sends the new user data stored in the CM 131 of the CMPK 130A,to the FMPK 144A via the BEPK 140A. As a result, the BEPK 140A storesthe new user data. Also, the data FMPK 144A stores the old user data andthe new user data. Both the new physical page address and the oldphysical page address are associated with the target logical pageaddress in the data FMPK 144A. The new physical page address indicatesthe physical page in which the new user data is stored, and the oldphysical page address indicates the physical page in which the old userdata is stored.

In the system state 2, the controller 100 sends the intermediate parityreception command to the data FMPK 144A and the intermediate paritytransmission command to the parity FMPK 144P. As a result, the systemstate transits to the state 3.

FIG. 36 shows an arrangement of data in the system state 3, according toEmbodiment 1. This state occurs after the completion of the intermediateparity reception command and the intermediate parity transmissioncommand by the controller 100. The intermediate parity reception commandsends the intermediate parity generated by the data FMPK 144A, to thebuffer 143 of the BEPK 140A. The intermediate parity transmissioncommand sends the intermediate parity of the buffer 143 of the BEPK 140Ato the parity FMPK 144P without being stored in the CM, and writes thenew parity generated by the parity FMPK 144P into the parity FMPK 144P.Accordingly, the buffer 143 of the BEPK 140A stores the new user dataand the intermediate parity. Both the new physical page address and theold physical page address are associated with the target logical pageaddress in the parity FMPK 144P. The new physical page address indicatesthe physical page in which the new parity is stored, and the oldphysical page address indicates the physical page in which the oldparity is stored. At least up to this stage, the correspondencerelationship between the target logical page address and the oldphysical page in which the old user data is stored is kept in the dataFMPK 144A. Therefore, when faults occur in the states 1 to 3, as will bedescribed hereinafter, transmitting the new data to the data FMPK 144Acan generate the intermediate parity.

In the system state 3, the controller 100 changes the process stageinformation of the SMs 132 to the post-parity update stage, whereby thesystem state transits to the state 4.

FIG. 37 shows an arrangement of data in the system state 4, according toEmbodiment 1. This state occurs after the transmission of theintermediate parity transmission command by the controller 100, aftercompletion of the writing of the new parity in the parity FMPK, andafter the MP updates the process stage information item stored in the SM132 to the post-parity generation stage. The process stage informationitem is stored in both the SM 132 of the CMPK 130A and the SM 132 of theCMPK 130B to obtain a redundant process stage information.

In the system state 4, the controller 100 sends the new data commitcommand to the data FMPK 144A. As a result, the system state transits tothe state 5.

FIG. 38 shows an arrangement of data in the system state 5, according toEmbodiment 1. This state occurs after the completion of the new datacommit command on the new user data by the controller 100. Accordingly,the old physical page address of the target entry 1449 in the data FMPK144A indicates the new user data, and the new physical page address iscleared. After the new parity is written to the physical page of the FMin the parity FMPK 144P, the old data stored in the data FMPK 144Abecomes no longer necessary. Mapping of the logical page and the oldphysical page in which the old data is stored is canceled by the newdata commit command, and thus the old physical page is erased. Thestorage device having the FMs needs empty regions in order for thereclamation process, a wear leveling process and the like to beperformed. In the present embodiment, therefore, the old data can beerased by not mapping the old data, as soon as the old data becomesunnecessary, so that empty blocks (free spaces) can be ensured in theFMs by executing appropriate processes.

In the system state 5, the controller 100 sends the new data commitcommand to the parity FMPK 144P. As a result, the system state transitsto the state 6.

FIG. 39 shows an arrangement of data in the system state 6, according toEmbodiment 1. This state occurs after the completion of the new datacommit command on the parity FMPK 144P by the controller 100. Therefore,the old physical page address of the target entry 1449 in the parityFMPK 144P indicates the new parity, and the new physical page address iscleared.

In the system state 6, the controller 100 clears the process stageinformation item stored in each SM 132, whereby the system statetransits to the system state 7.

FIG. 40 shows an arrangement of data in the system state 7, according toEmbodiment 1. This system state 7 occurs after the process stageinformation item stored in each SM 132 is cleared by the controller 100.As a result, both the SM 132 of the CMPK 130A and the SM 132 of the CMPK130B are cleared.

Next is described a restoration process that is executed when a systemfault occurs in each of the states 1 to 7.

The system fault here means a simultaneous point of fault occurring inthe plurality of MPPKs 120, the plurality of CMPKs 130, the plurality ofBEPKs 140, and the plurality of FMPKs 144. Upon the occurrence of thissystem fault, the number of faulty packages of one type is equal to orless than one. In addition, the occurrence of this system fault includesa simultaneous occurrence of faults in a plurality of types of pages. Aswill be described hereinafter, even upon a simultaneous occurrence offaults in a plurality of types of packages, the data thereof can berestored without being lost.

In the state 1, the occurrence of the system fault causes the systemstate to transit to the state a.

FIG. 41 shows an arrangement of data in the system state a, according toEmbodiment 1. This system state a means a situation where faults occurin the MPPK 120A in the write process, the CMPK 130A, the BEPK 140Ahaving the new user data stored therein, and the FMPK 144E having theother user data stored therein. The sections where the faults occur areshown by “X” in this diagram. In the diagram and the followingdescription, the MP 121 of the MPPK 120B that takes over the process bythe MPPK 120A in which a fault has occurred is referred to as“transition MP.” The transition MP detects that the process stageinformation stored in the SM 132 of the CMPK 130B indicates thepre-parity generation stage. In response to this detection, thetransition MP transmits the new data transmission command.

In the system state a, the controller 100 sends the new datatransmission command to the data FMPK 144A. As a result, the systemstate transits to the system state A.

FIG. 42 shows an arrangement of data in the system state A, according toEmbodiment 1. This system state A occurs after the completion of the newdata transmission command by the controller 100. The new datatransmission command sends the new user data stored in the CM 131 of theCMPK 130B free of faults to the data FMPK 144A via the BEPK 140B free offaults. Accordingly, the BEPK 140B has the new user data stored therein.The data FMPK 144A has the old user data and the new user data storedtherein. The new physical page address stored in the target entry 1449of the data FMPK 144A indicates the new user data.

In the system state A, the controller 100 sends the intermediate parityreception command to the data FMPK 144A and the intermediate paritytransmission command to the parity FMPK 144P. As a result, the systemstate transits to the state B.

FIG. 43 shows an arrangement of data in the system state B, according toEmbodiment 1. This state occurs after the completion of the intermediateparity reception command and the intermediate parity transmissioncommand by the BEPK 140. The intermediate parity reception command sendsthe intermediate parity, which is generated by the data FMPK 144A, tothe BEPK 140B. The intermediate parity transmission command sends theintermediate parity stored in the buffer of the BEPK 140B to the parityFMPK 144P without being stored in the CM 131, and writes the new paritygenerated by the parity FMPK 144P into the parity FMPK 144P.Accordingly, the BEPK 140B has the new user data and the intermediateparity stored therein. The parity FMPK 144P has the old parity and thenew parity stored therein.

In the system state B, the controller 100 changes the process stageinformation of each SM 132, whereby the system state transits to thesystem state C.

FIG. 44 shows an arrangement of data in a system state C, according toEmbodiment 1. This state occurs after the controller 100 completes theparity transmission command and updates the process stage informationstored in each SM 132. Thus, the SM 132 of the CMPK 130B indicates thepost-parity generation stage.

In the system state C, the controller 100 sends the new data commitcommand to the data FMPK 144A. As a result, the system state transits tothe system state D.

FIG. 45 shows an arrangement of data in a system state D, according toEmbodiment 1. This system state D occurs after the completion of the newdata commit command on the new user data by the controller 100. Thus,the old physical page address stored in the target entry 1449 of thedata FMPK 144A indicates the new user data, and the new physical pageaddress is cleared.

In the system state D, the controller 100 sends the new data commitcommand to the parity FMPK 144P, whereby the system state transits tothe system state E.

FIG. 46 shows an arrangement of data in the system state E, according toEmbodiment 1. This system state occurs after the completion of the newdata commit command on the new parity by the controller 100. Thus, theold physical page address stored in the target entry 1449 of the parityFMPK 144P indicates the new parity, and the new physical page address iscleared.

In the system state E, the controller 100 clears the process stageinformation of the SM 132, whereby the system state transits to thesystem state F.

FIG. 47 shows an arrangement of data in the system state F, according toEmbodiment 1. In this system state F, the process stage information itemstored in the SM 132 of the CMPK 130B is cleared. This system state Foccurs after the completion of the write process related to paritygeneration. When the system state transits to the system state F, it isdetermined that the write process is completed without causing dataloss.

As a result of the occurrence of a system fault in the system state 2,the system state transits to the system state b.

FIG. 48 shows an arrangement of data in the system state b, according toEmbodiment 1. As with the system state a, this system state b means asituation where faults occur in the MPPK 120A in the write process, theCMPK 130A, the BEPK 140A having the new user data stored therein, andthe FMPK 144E having the other user data stored therein. The transitionMP detects that the process stage information item stored in the SM 132of the CMPK 130B indicates the pre-parity generation stage. In responseto this detection, the transition MP transmits the new data transmissioncommand. In this system state b, because the old user data is associatedwith the logical page to which the new user data is to be written,transmission of the new user data can generate the intermediate parity.

In the system state b, the controller 100 sends the new datatransmission command to the data FMPK 144A, whereby the system statetransits to the state A. Thereafter, the system state can transit inorder of the system state B, the system state C, the system state D, thesystem state E, and the system state F.

As a result of the occurrence of the system fault in the system state 3,the system state transits to the system state c.

FIG. 49 shows an arrangement of data in the system state c, according toEmbodiment 1. As with the state a, this state means a situation wherefaults occur in the MPPK 120A in the write process, the CMPK 130A, theBEPK 140A having the new user data stored therein, and the FMPK 144Ehaving the other user data stored therein. The transition MP detectsthat the process stage information stored in the SM 132 of the CMPK 130Bindicates the pre-parity generation stage. In response to thisdetection, the transition MP transmits the new data transmissioncommand. The data FMPK 144A has the old user data and the new user datastored therein. In the target entry 1449 of the data FMPK 144A, the oldphysical page address indicates the old user data, and the new physicalpage address indicates the new user data. The parity FMPK 144P has theold parity and the new parity stored therein. In the target entry 1449of the parity FMPK 144P, the old physical page address indicates the oldparity, and the new physical page address indicates the new parity. Thedata FMPK in the system state c maintains the correspondencerelationship between the old user data and the logical page to which thenew user data is to be written. Therefore, the intermediate parity canbe generated by transmitting the new data.

In the system state c, the controller 100 sends the new datatransmission command to the data FMPK 144A, whereby the system statetransits to the state G.

FIG. 50 shows an arrangement of data in the system state G, according toEmbodiment 1. This system state G occurs after the completion of the newdata transmission command by the controller 100. As in the system stateA, the new data transmission command sends the new user data stored inthe CM 131 of the CMPK 130B free of faults to the data FMPK 144A via theBEPK 140B free of faults. Accordingly, the BEPK 140B stores the new userdata. The data FMPK 144A in the system state G maintains thecorrespondence relationship between the old user data and the logicalpage to which the new user data is to be written. Therefore, theintermediate parity can be generated by transmitting the new data.Moreover, the parity FMPK 144P in the state G maintains thecorrespondence relationship between the old parity and the targetlogical page. Thus, the new parity can be generated by transmitting theintermediate parity.

In the system state G, the controller 100 sends the intermediate parityreception command to the data FMPK 144A and the intermediate paritytransmission command to the parity FMPK 144P. As a result, the systemstate transits to the system state B. Subsequently, the system state cantransit in order of the system state C, the system state D, the systemstate E, and the system state F.

As a result of the occurrence of the system fault in the state 4, thesystem state transits to the state C. Subsequently, the system state cantransit in order of the system state D, the system state E, and thesystem state F.

As a result of the occurrence of the system fault in the system state 5,the system state transits to the system state e.

FIG. 51 shows an arrangement of data in the system state e, according toEmbodiment 1. As with the system state a, this system state e means asituation where faults occur in the MPPK 120A in the write process, theCMPK 130A, the BEPK 140A having the new user data stored therein, andthe FMPK 144E having the other user data stored therein. The transitionMP detects that the process stage information stored in the SM 132 ofthe CMPK 130B indicates the post-parity generation stage. In otherwords, this state occurs after the completion of the parity transmissioncommand by the controller 100 and after the process stage informationstored in the SM 132 is updated. In response to the detection, thetransition MP transmits the new data commit command to the data FMPK144A. The data FMPK 144A has the new user data stored therein. In thetarget entry 1449 of the data FMPK 144A, the old physical page addressindicates the new user data. The parity FMPK 144P has the old parity andthe new parity stored therein. In the target entry 1449 of the parityFMPK 144P, the old physical page address indicates the old parity, andthe new physical page address indicates the new parity.

In the system state e, the controller 100 sends the new data commitcommand to the data FMPK 144A, whereby the system state transits to thestate D. Subsequently, the system state can transit from the systemstate E to the system state F.

As a result of the occurrence of the system fault in the system state 6,the system state transits to the system state f.

FIG. 52 shows an arrangement of data in the system state f, according toEmbodiment 1. As with the system state a, this state means a situationwhere faults occur in the MPPK 120A in the write process, the CMPK 130A,the BEPK 140A having the new user data stored therein, and the FMPK 144Ehaving the other user data stored therein. The transition MP detectsthat the process stage information item stored in the SM 132 of the CMPK130B indicates the post-parity generation stage. In other words, thisstate occurs after the completion of the parity transmission command bythe controller 100 and after the process stage information item storedin the SM 132 is updated. Accordingly, the transition MP transmits thenew data commit command to the data FMPK 144A. The data FMPK 144A storesthe new user data. In the target entry 1449 of the data FMPK 144A, theold physical page address indicates the new user data. The parity FMPK144P stores the new parity. In the target entry 1449 of the parity FMPK144P, the old physical page address indicates the new parity.

In the system state f, the controller 100 sends the new data commitcommand to the data FMPK 144A, whereby the system state transits to thestate I.

FIG. 53 shows an arrangement of data in the system state I, according toEmbodiment 1. As with the system state a, this system state I means asituation where faults occur in the MPPK 120A in the write process, theCMPK 130A, the BEPK 140A having the new user data stored therein, andthe FMPK 144E having the other user data stored therein. This stateoccurs after the completion of the new data commit command on the newuser data by the controller 100. In response to the detection, thetransition MP transmits the new data commit command to the parity FMPK144P. The data FMPK 144A has the new user data stored therein. In thetarget entry 1449 of the data FMPK 144A, the old physical page addressindicates the new user data. The parity FMPK 144P has the new paritystored therein. In the target entry 1449 of the parity FMPK 144P, theold physical page address indicates the new parity.

In the system state I, the controller 100 sends the new data commitcommand to the parity FMPK 144P, whereby the system state transits tothe state E. Subsequently, the system state can transit to the systemstate F.

As a result of the occurrence of a system fault in the system state 7,the system state transits to the system state F. In the system state 7the data stored in the FMPKs 144 are determined and the process stageinformation items are cleared. Therefore, no additional processes arerequired even when the system fault occurs and the system stateconsequently transits to the state F. Therefore, even upon theoccurrence of a system fault, the host computer 30 can read oDi and oD1to oDy free of faults that are shown in the stripes of the RAID, as longas the system state can transit to the system state 7 or the state F.Therefore, data loss does not occur because the host computer 30 canalso read oDx in which a fault occurs, by XORing the oD1 . . . nDi . . .oDy, nP within the stripes.

In this embodiment, the number of the MPPKs 120, the CMPKs 130, and theBEPKs 140 are each two but may be three or more. Even when the number ofthe MPPKs 120, the CMPKs 130, or the BEPKs 140 is one, the sameoperations can be carried out as long as no faults occur in a sectionthereof.

According to the state transitions described above, data loss does notoccur, even when the system fault occurs in any of the system states 1to 7. In other words, data loss does not occur even when thesimultaneous point of fault occurs in the plurality of MPPKs 120, theplurality of CMPKs 130, the plurality of BEPKs 140 and the plurality ofFMPKs 144. Thus, the reliability of the storage system 10 can beimproved. Note that the present embodiment can couple the other storagesystems having the XOR function in place of the FMPKs 144 and cause theother storage devices to implement the intermediate parity and/or paritycalculation process.

Furthermore, because overwriting of data cannot be performed in a normalflash memory, the new physical page is allocated to the logical page ina normal write process.

The present embodiment uses the data that are stored in the old physicalpage which is disabled as a result of the allocation of the new physicalpage. Therefore, the present embodiment does not increase the number oftimes the write process is performed and the number of times the data iserased. In other words, in the present embodiment, the operating life ofthe flash memory is not shortened.

Embodiment 2

This embodiment illustrates a situation where the FMPK 144 supports theXOR function based on a request regarding a SCSI command. Examples ofthe SCSI command include XDWRITE, XDREAD, and XPWRITE. The rest of theconfigurations of the storage system 10 are the same as those describedin Embodiment 1. In the present embodiment, the storage media are notlimited to the flash memory devices as long as these SCSI commands aresupported.

Write Process According to Embodiment 2

A normal write process is now described.

FIG. 54 shows a write process according to Embodiment 2. In thissequence diagram as well, the DFa and the DFb of the data FMPK 144Arepresent the memory 1445 and the FM 1443 (physical page) of the dataFMPK 144A. Furthermore, the DFa and the DFb of the parity FMPK 144Prepresent the memory 1445 and the FM 1443 (physical page) of the parityFMPK 144P. The other key components of the operations in the sequencediagram are the same as those shown in the sequence diagram illustratingthe write process according to Embodiment 1.

In the present embodiment, the process stage information items stored inthe SMs 132 indicate “pre-parity generation stage,” “stage in process ofdata media update,” “stage in process of parity media update,” and“post-parity generation stage.” Compared to Embodiment 1, the presentembodiment has more of the process stage information items stored in theSMs 132. First, the MP 121 performs the processes S2110 to S2350, as inthe write process of Embodiment 1. The MP 121 accordingly changes thevalues of the process stage information items stored in the two SMs 132corresponding to the regions of the two CMs 131 having the new user datastored therein, to values corresponding to the stage in process of datamedia update.

Next, the MP 121 sends an XDWRITE command to the data FMPK 144A (S6210).This XDWRITE command designates the logical page in which the old userdata is stored, and accompanies the new user data. At this moment, inresponse to an instruction from the MP 121, the BEPK 140 secures thebuffer 143, reads the new user data from the CM 131, and writes the newuser data into the secured buffer 143. The MP 121 then reads the newuser data from the buffer 143 and sends the new user data to the dataFMPK 144A.

The data FMPK 144A then receives the XDWRITE command and the new userdata from the controller 100. The data FMPK 144A accordingly writes thenew user data into the FM 1443. Subsequently, the data FMPK 144A readsthe old user data and the new user data stored in the FM 1443, generatesthe intermediate parity using the XOR circuit 1442, and writes theintermediate parity into the memory 1445. The data FMPK 144A then sendsa normal end of the XDWRITE command the controller 100.

Thereafter, the MP 121 receives the normal end of the XDWRITE commandfrom the data FMPK 144A. The MP 121 accordingly sends an XDREAD commandto the data FMPK 144A (S6220). This XDREAD command designates theaddress of the memory 1445 having the intermediate parity storedtherein. Note that the address of the memory 1445 having theintermediate parity stored therein is stored in the memory 1445.

The data FMPK 144A then receives the XDREAD command from the controller100. The data FMPK 144A accordingly reads the intermediate parity storedin the memory 1445 on the basis of information in the memory 1445, sendsthe intermediate parity to the controller 100, and sends a normal end ofthe XDREAD command to the controller 100.

At this moment, the BEPK 140 receives the intermediate parity from thedata FMPK 144A and writes the intermediate parity into the buffer 143.Next, the MP 121 receives the normal end of the XDREAD command from thedata FMPK 144A. The MP 121 accordingly changes the values of the processstage information items to a mid-stage of parity media update.

The MP 121 then sends an XPWRITE command to the parity FMPK 144P(S6410). This XPWRITE command designates the logical page having the oldparity stored therein, and accompanies the intermediate parity. At thismoment, in response to an instruction from the MP 121, the BEPK 140reads the intermediate parity from the buffer 143 and sends theintermediate parity to the parity FMPK 144P.

Next, the parity FMPK 144P receives the XPWRITE command and theintermediate parity from the controller 100. The parity FMPK 144Paccordingly receives the intermediate parity and writes the intermediateparity into the memory 1445. As a result of the XOR operation on the oldparity stored in the PFb and the intermediate parity stored in thememory 1445, the parity FMPK 144P generates the new parity and writesthe same into the FM 1443. Subsequently, the parity FMPK 144P sends anormal end of the XPWRITE command to the controller 100.

Thereafter, the MP 121 clears the process stage information items storedin the SM 132.

The Above is the Write Process.

As described above, the controller 100 sends the intermediate parityfrom the buffer 143 to the parity FMPK 144P without writing theintermediate parity received from the data FMPK 144A into the CM 131.Accordingly, the number of accesses to the CM 131 during the writeprocess becomes three, thereby the number of accesses to the CM 131 canbe reduced (see paragraph [0208]).

According to this embodiment, the reliability of the storage system 10can be improved by storing the new user data and each process stageinformation in two CMPKs 130.

In addition, this embodiment can increase the speed of the storagesystem 10 because the new data commit commands (in S3230 and S3320) arenot required.

According to this embodiment, the storage medium employed for thestorage system 10 may be a magnetic storage medium, an optical storagemedium, or other nonvolatile storage medium.

Specific Examples of Transition Write Process According to Embodiment 2

Several specific examples of the transition write process performed uponthe occurrence of the MP fault are now described.

First Specific Example of Transition Write Process According toEmbodiment 2

Here is described the transition write process that is performed uponthe occurrence of the MP fault in the pre-parity generation stage.

FIG. 55 shows a transition write process performed upon the occurrenceof an MP fault in the pre-parity generation, according to Embodiment 2.The operation targets of the operations shown in this sequence diagramare the same as those shown in the sequence diagrams related to thenormal write process.

Once the MP 121 free of faults recognizes that a fault has occurred inanother MP 121, the MP 121 acknowledges that each process stageinformation indicates the pre-parity generation. The MP 121 accordinglychanges the values of the process stage information items stored in thetwo SMs 132 corresponding to the regions of the two CMs 131 having thenew user data stored therein, to the data media update.

Next, the MP 121 performs the processes S6210 to S6410, as in the normalwrite process. In other words, the MP 121 free of faults takes over thewrite process, from the point where the XDWRITE command is sent to thedata FMPK 144A (S6210). Because the new user data is stored in the CM131, the BEPK 140 reads the new user data from the CM 131, writes thenew user data into the buffer 143, reads the new user data from thebuffer 143, and sends the new user data to the data FMPK 144A, inresponse to the instruction from the MP 121. In this manner, the MP 121free of faults can take over the write process to perform the writeprocess successfully.

Subsequently, the MP 121 clears the process stage information itemsstored in the SMs 132.

The above is the transition write process.

As described above, even when the MP fault occurs in the pre-paritygeneration stage, another MP 121 free of faults can take over the writeprocess to perform the write process successfully based on the processstage information items stored in the SMs 132. When the process stageinformation item obtained upon the occurrence of the MP fault indicatesthe pre-parity generation stage, the MP 121 takes over the writeprocess, from the point where the XDWRITE command is sent to the dataFMPK 144A (S6210).

Second Specific Example of Transition Write Process According toEmbodiment 2

Here is described the transition write process that is performed uponthe occurrence of the MP fault in the mid-stage of data media update.

FIG. 56 shows a transition write process performed upon the occurrenceof the MP fault in the mid-stage of data media update, according toEmbodiment 2. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process. In the diagram and the following description, the userdata other than the old user data stored in the RAID groups configuredby the plurality of FMPKs 144 are referred to as “other user data.” TheFMPK 144 having the other user data stored therein is referred to as“other data FMPK 144E.” In the diagram and the following description,the other user data are referred to as “oD1, . . . , oDn.”

Once the MP 121 free of faults recognizes a fault occurring in anotherMP 121, the MP 121 acknowledges that each process stage information itemindicates the state in process of data media update. The MP 121accordingly sends the normal read (READ) command to the other data FMPK144E (S6510). In other words, the MP 121 free of faults takes over thewrite process, from the point where the new parity is generated. Thisnormal read command designates the logical page having the other userdata stored therein. The other data FMPK 144E accordingly reads theother user data and sends the other user data to the controller 100.Consequently, the BEPK 140 writes the other user data into the buffer143 and further writes the other user data into the CM 131.

Next, the MP 121 performs the XOR operation on the new user data and theother user data stored in the CM 131, generates the new parity, andwrites the new parity into the two CMs 131 (S6520). The MP 121 thenwrites a value indicating the post-parity generation into the processstage information items stored in the two SMs 132 corresponding to thetwo CMs 131.

Subsequently, the MP 121 sends the normal write (WRITE) command to thedata FMPK 144A (S6530). This normal write command accompanies the newuser data. Consequently, the BEPK 140 writes the new user data stored inthe CM 131 into the buffer 143, and sends the new user data to the dataFMPK 144A. The data FMPK 144A accordingly writes the new user data intothe FM 1443.

Subsequently, the MP 121 sends the normal write command to the parityFMPK 144P (S6540). This normal write command accompanies the new parity.Consequently, the BEPK 140 writes the new parity stored in the CM 131into the buffer 143, and sends the new parity to the parity FMPK 144P.The parity FMPK 144P accordingly writes the new parity into the FM 1443.

The MP 121 then clears the process stage information items stored in theSM 132.

The above is the transition write process.

As described above, even when the MP fault occurs in the mid-stage ofdata media update, the other MPs 121 can take over the write process toperform the transition write process. When the process stage informationitems during the occurrence of MP fault are being data-media updated,the MP 121 free from a fault takes over a write process from a stage inwhich other data are transferred from the FMPK to the CM 131.

Third Specific Example of Transition Write Process According toEmbodiment 2

Here is described a transition write process performed upon theoccurrence of the MP fault in the mid-stage of parity media update.

FIG. 57 shows a transition write process performed upon the occurrenceof the MP fault in the mid-stage of parity media update, according toEmbodiment 2. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes that a fault has occurred inanother MP 121, the MP 121 acknowledges that each process stageinformation indicates the mid-stage of parity media update. The MP 121accordingly performs S6510, S6520 and S6540 described above (see FIG.56). Consequently, the new parity stored in the CM 131 is written to theparity FMPK 144P.

Subsequently, the MP 121 clears the process stage information itemsstored in the SM 132.

The above is the transition write process.

As described above, even when the MP fault occurs in the mid-stage ofparity media update, the other MPs 121 can take over the write processto perform the transition write process. When the process stageinformation items during the occurrence of MP fault are beingparity-media updated, a write process is taken over from a stage inwhich other data are transferred from the FMPK 144E to the CM 131.

Fourth Specific Example of Transition Write Process According toEmbodiment 2

Here is described a transition write process performed upon theoccurrence of an MP fault in the post-parity generation stage.

FIG. 58 shows a transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 2. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes an MP 121 in which a fault hasoccurred, the MP 121 acknowledges that each process stage informationindicates the post-parity generation. The MP 121 accordingly performsS6530 and S6540 described above. Consequently, the new user data storedin the CM 131 is written to the data FMPK 144A. Furthermore, the newparity stored in the CM 131 is written to the parity FMPK 144P.

Subsequently, the MP 121 clears the process stage information itemsstored in the SM 132.

The above is the transition write process.

As described above, even when the MP fault occurs in the post-paritygeneration stage, the other MPs 121 free from faults can take over thewrite process to perform the transition write process. Similarly, dataloss does not occur even when the simultaneous point of fault occurs inthe plurality of MPPKs 120, the plurality of CMPKs 130, and theplurality of BEPKs 140. Thus, the reliability of the storage system 10can be improved. In the case where the process stage informationobtained upon the occurrence of the MP fault indicates the post-paritygeneration stage, the MP 121 free of faults takes over the writeprocess, from the point where the new user data is written to the dataFMPK 144A and the new parity is written to the parity FMPK 144P.

Operations by FMPK 144 Based on Command, According to Embodiment 2

An operation by the FMPK 144 based on each command is describedhereinafter.

FIG. 59 shows an operation performed based on the normal read command,according to Embodiment 2. In the following description, the logicalpage that is designated by a command sent from the controller 100 to theFMPK 144 is referred to as “target logical page.” Of the entries of thepointer table shown in the memory 1445 of the FMPK 144, the entrycorresponding to the target logical page is referred to as “target entry1449.” The target entry 1449 has a field for a logical page address,which is a logical address designating the target logical page, and afield for a physical page address, which is a physical addressdesignating a physical page corresponding to the target logical page. Inthe diagram and the following description, in the target entry 1449, thelogical page address is called “LA,” and the old physical page addressis called “PA.” In addition, the value of the logical page address isdescribed as “LBA xxxx,” and the values of the physical page address aredescribed as “p0” and “p1.”

In Embodiment 2, the FMPK 144 receiving the normal read command is thesame as the other data FMPK 144E. First, the other data FMPK 144Ereceives the normal read command from the BEPK 140 of the controller 100(S7110). This normal read command designates the target logical pagehaving the old data stored therein. The other data FMPK 144E then readsthe old data from the old physical page designated by the physical pageaddress of the target entry 1449 (S7120). The other data FMPK 144E thensends a data response including the old data to the controller 100(S7130).

FIG. 60 shows an operation performed based on the normal write command,according to Embodiment 2. In Embodiment 2, the FMPK 144 receiving thenormal write command is the same as the data FMPK 144A or the parityFMPK 144P. First, the FMPK 144A or 144P receives the normal writecommand from the BEPK 140 of the controller 100 (S7210). This normalwrite command designates the target logical page having the old datastored therein, and accompanies the new data. The FMPK 144A or 144P thenwrites the new data into a new physical page different from the oldphysical page (S7220). The FMPK 144A or 144P then performs the pointerconnection on the new data by designating the new physical page for thephysical page address of the target entry 1449 (S7230). Subsequently,the FMPK 144A or 144P sends a normal end response to the controller 100(S7240).

FIG. 61 shows an operation performed based on the XDWRITE command,according to Embodiment 2. In Embodiment 2, the FMPK 144 receiving theXDWRITE command is the same as the data FMPK 144A. First, the data FMPK144A receives the XDWRITE command from the BEPK 140 of the controller100 (S7310). This XDWRITE command designates the target logical pagehaving the old data stored therein, and accompanies the new data. Thedata FMPK 144A then writes the new data into the new physical pagedifferent from the old physical page (S7320). Next, the data FMPK 144Areads the old data stored in the old physical page and the new datastored in the new physical page, generates the intermediate parity usingthe XOR circuit 1442, and writes the intermediate parity into the memory1445 (S7330). The data FMPK 144A then performs the pointer connection onthe new data by designating the new physical page for the physical pageaddress of the target entry 1449 (S7340). Subsequently, the FMPK 144sends a normal end response to the controller 100 (S7350). With thisXDWRITE command, the intermediate parity can be written into the memory1445 and the new data can be determined, while reducing the load imposedon the CM 131 and the number of accesses to the data FMPK 144A. In thepresent embodiment, the new data commit command (S3230 and S3320)described in Embodiment 1 is not required for determining the datastored in the FMPK 144.

FIG. 62 shows an operation performed based on the XDREAD command,according to Embodiment 2. In Embodiment 2, the FMPK 144 receiving theXDREAD command is the same as the data FMPK 144A in which theintermediate parity is written for the memory 1445. First, the data FMPK144A receives the XDREAD command from the BEPK 140 of the controller 100(S7410). This XDREAD command designates the address having theintermediate parity therein. The data FMPK 144A then reads theintermediate parity stored in the memory 1445 (S7420). The data FMPK144A then sends a data response including the intermediate parity to thecontroller 100 (S7430).

FIG. 63 shows an operation performed based on the XPWRITE command,according to Embodiment 2. In Embodiment 2, the FMPK 144 receiving theXPWRITE command is the same as the parity FMPK 144P. First, the parityFMPK 144P receives the XPWRITE command from the BEPK 140 of thecontroller 100 (S7510). This XPWRITE command designates the targetlogical page having the old parity stored therein, and accompanies theintermediate parity. The parity FMPK 144P then writes the intermediateparity into the memory 1445 (S7520). Next, the parity FMPK 144 reads theold parity from the old physical page indicated by the physical pageaddress of the target entry 1449, reads the intermediate parity from thememory 1445, generates the new parity using the XOR circuit 1442, andwrites the new parity into the new physical page different from the oldphysical page (S7530). The parity FMPK 144P then performs the pointerconnection on the new parity by designating the new physical page forthe physical page address of the target entry 1449 (S7540).Subsequently, the parity FMPK 144P sends an end response to thecontroller 100 (S7550). This XPWRITE process can generate and determinethe new parity, while reducing the load imposed on the CM 131 and thenumber of accesses made to the data FMPK 144A. In the presentembodiment, the new data commit command (S3230 and S3320) described inEmbodiment 1 is not required for determining the data.

Embodiment 3

As with Embodiment 2, this embodiment illustrates a situation where theFMPK 144 supports the XOR function of the standard SCSI command. Therest of the configurations of the storage system 10 are the same asthose described in Embodiment 1.

As with Embodiment 2, in the present embodiment the process informationitem stored in the SM 132 indicates “pre-parity generation stage,”“stage in process of data media update,” “stage in process of paritymedia update,” and “post-parity generation stage.”

Write Process According to Embodiment 3

A normal write process is now described.

FIG. 64 shows a write process according to Embodiment 3. In thissequence diagram as well, the DFa and the DFb of the data FMPK 144Arepresent the memory 1445 and the FM 1443 (physical page) of the dataFMPK 144A. Furthermore, the DFa and the DFb of the parity FMPK 144Prepresent the memory 1445 and the FM 1443 (physical page) of the parityFMPK 144P. The key components of the operations in this sequence diagramare the same as those shown in the sequence diagram illustrating thewrite process according to Embodiment 2.

First, the MP 121 performs the processes S2110 to S2350, as in the writeprocesses according to Embodiments 1 and 2. As in the write processaccording to Embodiment 2, the MP 121 accordingly changes the values ofthe process stage information items stored in the two SMs 132corresponding to the regions of the two CMs 131 having the new user datastored therein, from the value corresponding to the pre-paritygeneration stage to the value corresponding to the stage in process ofdata media update. The present embodiment can cope with a simultaneouspoint of fault in the MP 121 or the CM 131.

The MP 121 then sends the normal read command to the data FMPK 144A(S6110). This normal read command designates the logical page having theold user data stored therein. The data FMPK 144A accordingly reads theold user data and sends the old user data to the controller 100.Consequently, the BEPK 140 writes the old user data into the buffer 143and further writes the old user data into the two CMs 131. Next, the MP121 writes the value indicating the mid-stage of data media update intothe process stage information items stored in the two SMs 132corresponding to the two CMs 131.

Subsequently, as in the write process according to Embodiment 2, the MP121 sends the XDWRITE command to the data FMPK 144A (S6210). ThisXPWRITE command designates the logical page having the old user datastored therein, and accompanies the new user data. Accordingly, in thedata FMPK 144A, the new user data is stored and the intermediate parityis stored in the memory 1445.

Subsequently, as in the write process according to Embodiment 2, the MP121 sends the XDREAD command to the data FMPK 144A (S6220). This XDREADcommand designates the logical page having the intermediate paritystored therein. Consequently, the intermediate parity is stored in thebuffer 143 of the BEPK 140.

The MP 121 then sends the normal read command to the parity FMPK 144P(S6310). This normal read command designates the logical page having theold parity stored therein. The parity FMPK 144P accordingly reads theold parity and sends the old parity to the controller 100. Consequently,the BEPK 140 writes the old parity into the buffer 143 and furtherwrites the old parity into the two CMs 131. The MP 121 then changes thevalues of the process stage information items to the mid-stage of paritymedia update.

Subsequently, as in the write process according to Embodiment 2, the MP121 sends the XPWRITE command to the parity FMPK 144P (S6410). ThisXPWRITE command designates the logical page having the old parity storedtherein, and accompanies the intermediate parity. Accordingly, the newparity is stored in the parity FMPK 144P.

The MP 121 then clears the process stage information items stored in theSM 132.

The Above is the Write Process.

As described above, the controller 100 writes the old user data receivedfrom the data FMPK 144A and the old parity received from the parity FMPK144P into the CM 131, but sends the intermediate parity from the buffer143 to the parity FMPK 144P without writing the intermediate parityreceived from the data FMPK 144A into the CM 131. Therefore, the numberof accesses to the CM 131 during the write process becomes seven,thereby the number of accesses to the CM 131 can be reduced.Accordingly, the number of accesses to the CM 131 in the write processcan be reduced, lowering the number of accesses to the CM 131 andimproving the write process performance of the storage system.

In addition, according to the present embodiment, the new user data, theold user data, the old parity, and each of the process stage informationitems are stored in the two CMPKs 130. Therefore, even when one of thedata items is lost, the other data can be used, improving thereliability of the storage system 10.

Transition Write Process According to Embodiment 3

Several specific examples of the transition write process are nowdescribed.

First Specific Example of Transition Write Process According toEmbodiment 3

Here is described the transition write process that is performed uponthe occurrence of the MP fault in the pre-parity generation stage.

FIG. 65 shows a transition write process performed upon the occurrenceof an MP fault in the pre-parity generation stage, according toEmbodiment 3. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes the MP 121 having a fault, theMP 121 acknowledges that each process stage information item indicatesthe pre-parity generation stage. The MP 121 accordingly performs theprocesses S6110 to S6410, as in the normal write process. In otherwords, the MP 121 free of faults takes over the write process, from thepoint where the XDWRITE command is sent to the data FMPK 144A (S6210).Because the new user data is stored in the CM 131, the BEPK 140, inresponse to the instruction from the MP 121, reads the new user datafrom the CM 131, writes the new user data into the buffer 143, reads thenew user data from the buffer 143, and sends the new user data to thedata FMPK 144A. As a result, the MP 121 free of faults can take over thewrite process and perform the write process successfully.

The MP 121 then clears the process stage information items stored in theSM 132.

The Above has Described the Transition Write Process.

As described above, even when the MP fault occurs in the pre-paritygeneration stage, the other MPs 121 free from faults can take over thewrite process to perform the transition write process on the basis ofthe process stage information.

Second Specific Example of Transition Write Process According toEmbodiment 3

Here is described the transition write process that is performed uponthe occurrence of the MP fault in the mid-stage of data media update.

FIG. 66 shows a transition write process performed upon the occurrenceof the MP fault in the mid-stage of data media update, according toEmbodiment 3. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes an MP fault, the MP 121acknowledges that each process stage information indicates the datamedia update. The MP 121 accordingly sends the normal write command tothe data FMPK 144A (S6010). This normal write command accompanies theold user data. At this moment, in response to an instruction from the MP121, the BEPK 140 reads the old user data from the CM 131, writes theold user data into the buffer 143, reads the old user data from thebuffer 143, and sends the old user data to the data FMPK 144A.

The MP 121 then performs the processes S6110 to S6410, as in the normalwrote process. In other words, when the process stage information itemindicates the stage in process of data media update, the MP 121 free offaults takes over the write process, from the stage where the normalread command is sent to the data FMPK 144A (S6110).

Subsequently, the MP 121 clears the process stage information itemsstored in the SM 132.

The above is the transition write process.

As described above, even when the MP fault occurs in the mid-stage ofdata media update, the other MPs 121 free from faults can take over thewrite process to perform the transition write process on the basis ofthe process stage information.

Third Specific Example of Transition Write Process According toEmbodiment 3

Here is described a transition write process performed upon theoccurrence of the MP fault in the mid-stage of parity media update.

FIG. 67 shows a transition write process performed upon the occurrenceof the MP fault in the mid-stage of parity media update, according toEmbodiment 3. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes an MP having a fault, the MP121 acknowledges that each process stage information item indicates thestage in process of parity media update. The MP 121 accordingly readsthe old user data, the old parity, and the new user data stored in theCM 131, generates the new parity by means of the XOR operation, andwrites the new parity into the two CMs 131 (S6020). In other words, wheneach process stage information item indicates the stage in process ofparity media update, the MP 121 free of faults takes over the writeprocess, from the point where the new parity is generated from the olduser data, the old parity, and the new user data that are stored in theCM 131.

The MP 121 then performs the process S6410, as in the normal writeprocess.

Subsequently, the MP 121 clears the process stage information itemsstored in the SM 132.

The above is the transition write process.

As described above, even when the MP fault occurs in the mid-stage ofparity media update, the other MPs 121 free from faults can take overthe write process to perform the transition write process on the basisof the process stage information.

In this embodiment, the storage device of the storage unit 200 is notlimited to the FM 1443.

According to this embodiment, the simultaneous point of fault occurringin the MPPKs 120 and the FMPKs 144 configuring the RAID groups inprocess of destaging can be tolerated, preventing the occurrence of dataloss. Destaging here means writing the data stored in the CM 131 intothe FM 1443 of the FMPK 144. Similarly, even when the simultaneous pointof fault occurs in the plurality of MPPKs 120, the plurality of CMPKs130, the plurality of BEPKs 140, and the plurality of FMPKs 144, dataloss does not occur. Therefore, the reliability of the storage system 10can be improved. Therefore, the reliability of the storage system 10 canbe improved.

Embodiment 4

The rest of the configurations of the storage system 10 are the same asthose described in Embodiment 1.

Write Process According to Embodiment 4

A normal write process is now described.

FIG. 68 shows a write process according to Embodiment 4. The operationtargets in this sequence diagram are the same as those shown in thesequence diagram illustrating the write process according to Embodiment1.

In the present embodiment, an old data transmission command, new datatransmission command, and new data commit command are defined as the I/Ocommands sent from the controller 100 to the FMPKs 144. Moreover, in thepresent embodiment, the process stage information items stored in theSMs 132 indicate the pre-parity generation and post-parity generationstages.

For the purpose of illustration, the state of the parity FMPK 144P inthe write process is referred to as “FMPK state.” Several states of theFMPK 144 are defined hereinafter.

First, the MP 121 performs the processes S2110 to S2350, as in the writeprocess according to Embodiment 1. The MP 121 accordingly registers thevalues of the process stage information items stored in the two SMs 132,as the pre-parity generation stage, as in the write process according toEmbodiment 1.

The MP 121 then sends the normal read command to the data FMPK 144A(S8110). This normal read command designates the logical page having theold user data stored therein. Accordingly, the data FMPK 144A reads theold user data from the FM 1443, sends the old user data to thecontroller 100, and notifies the controller 100 of a normal end of thenormal read command.

At this moment, the BEPK 140 receives the old user data from the dataFMPK 144A, and writes the old user data into the buffer 143.

Subsequently, the MP 121 is notified by the data FMPK 144A of the normalend of the normal read command.

The state of the parity FMPK 144P obtained at this moment is referred toas “FMPK state 1a.” FIG. 71 shows the FMPK state of the parity FMPK144P.

The MP 121 then sends the old data transmission command to the parityFMPK 144P (S8120). This old data transmission command designates thelogical page having the old parity stored therein, and accompanies theold user data. At this moment, in response to an instruction from the MP121, the BEPK 140 reads the old user data from the buffer 143, and sendsthe old user data to the parity FMPK 144P. Because the MPPK 120 iscoupled to the CMPK 130 and the BEPK 140 by the internal networks, theMPPK 120 can control storage of data in the CMPK 130 and the BEPK 140.Therefore, after being read from the data FMPK 144 and stored in thebuffer of the BEPK 140, the old user data can be transferred to theparity FMPK 144P without being stored in the CM 131, reducing the accessload imposed on the CM 131.

Subsequently, the parity FMPK 144P receives the old data transmissioncommand and the old user data from the controller 100. The parity FMPK144P accordingly writes the old user data into the FM 1443, and notifiesthe controller 100 of a normal end of the old data transmission command.

Thereafter, the MP 121 is notified by the parity FMPK 144P of the normalend of the old data transmission command.

The state of the parity FMPK 144P obtained at this moment is referred toas “FMPK state 2a.” FIG. 72 shows the FMPK state of the parity FMPK144P.

Accordingly, the MP 121 sends the new data transmission command to theparity FMPK 144P (S8130). This new data transmission command designatesthe logical page having the old user data and the old parity storedtherein, and accompanies the new user data. At this moment, in responseto an instruction from the MP 121, the BEPK 140 reads the new user datafrom the CM 131, writes the new user data into the buffer 143, reads thenew user data from the buffer 143, and sends the new user data to theparity FMPK 144P.

Next, the parity FMPK 144P receives the new data transmission commandand the new user data from the controller 100. The operations performedby the FMPK 144P based on the new data transmission command in thisembodiment are different from those described in Embodiment 1.Consequently, the parity FMPK 144P writes the new user data into thememory 1445, reads the old user data and the old parity from the FM1443, generates the new parity by means of the XOR circuit 1442, andwrites the new parity into the FM 1443. The parity FMPK 144P thennotifies the controller 100 of a normal end of the new data transmissioncommand.

The MP 121 is then notified by the parity FMPK 144P of the normal end ofthe new data transmission command. Accordingly, the MP 121 changes thevalue of each process stage information item to the post-paritygeneration stage.

The state of the parity FMPK 144P obtained at this moment is referred toas “FMPK state 3a.” FIG. 73 shows the FMPK state of the parity FMPK144P.

Subsequently, the MP 121 sends the normal write command to the data FMPK144A (S8140). This normal write command accompanies the new user data.At this moment, in response to an instruction from the MP 121, the BEPK140 reads the new user data from the buffer 143, and sends the new userdata to the data FMPK 144A. At this moment, the BEPK 140 transmits thenew user data, which is stored in the buffer in S8130, to the data FMPK144A. Since the MPPK 120 can control the CMPK 130 and the BEPK 140, itis not necessary to read the new user data from the CMPK 130 again.Therefore, the access load imposed on the CMPK 130 can be reduced.

Next, the data FMPK 144A receives the normal write command and the newuser data from the controller 100. The data FMPK 144A accordingly writesthe new user data into the FM 1443, and notifies the controller 100 of anormal end of the normal write command. The normal write command isprocessed in the same manner as shown in FIG. 31.

Subsequently, the MP 121 is notified by the data FMPK 144A of the normalend of the normal write command. Accordingly, the MP 121 sends the newdata commit command to the parity FMPK 144P (S8150). This new datacommit command designates the logical page having the new parity storedtherein.

Next, the parity FMPK 144P receives the new data commit command from thecontroller 100. Accordingly, the parity FMPK 144P determines the newparity as the parity after update, and notifies the controller 100 of anormal end of the new data commit command.

Then, the MP 121 is notified by the parity FMPK 144P of the normal endof the new data commit command. Accordingly, the MP 121 clears the valueof each process stage information item.

The Above is the Write Process.

In this manner, the controller 100 sends the old user data from thebuffer 143 to the parity FMPK 144P without writing the old user datareceived from the data FMPK 144A into the CM 131. As a result, thenumber of accesses to the CM 131 during the write process becomes three,thereby the number of accesses to the CM 131 can be reduced.

According to this embodiment, the reliability of the storage system 10can be improved by storing the new user data and each process stageinformation item in the two CMPKs 130.

Specific Examples of Transition Write Process According to Embodiment 4

Several specific examples of the transition write process performed uponthe occurrence of an MP fault are now described hereinafter. By storingthe process stage information item in the SM 132 at an appropriatestage, another MP 121 free of faults can take over the write processwhen a fault occurs in a certain MP 121, without causing data loss.

First Specific Example of Transition Write Process According toEmbodiment 4

Here is described a transition write process that is performed upon theoccurrence of the MP fault in the pre-parity generation stage.

FIG. 69 shows the transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 4. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes the MP 121 fault, the MP 121acknowledges that each process stage information item of the SM 132indicates the pre-parity generation stage. Accordingly, the MP 121performs the processes S8110 to S8150, as in the normal write process.

The MP 121 then clears the process stage information items stored in theSM 132.

The above is the first specific example of the transition write process.In the present embodiment, it is guaranteed that the old user dataexisting in the data FMPK 144A can be read as long as the process stageinformation item indicates the pre-parity generation stage. Therefore,the MP 121 that carries out the transition process can take over thewrite process, from the point where the old user data is read (S8110),and complete the write process.

Second Specific Example of Transition Write Process According toEmbodiment 4

FIG. 70 shows a transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 4. The operation targets shown in this sequence diagram arethe same as those shown in the sequence diagrams related to the normalwrite process.

Once the MP 121 free of faults recognizes a fault in another MP 121, theMP 121 acknowledges that each process stage information item of the SM132 indicates the post-parity generation stage. Accordingly, the MP 121transfers the new user data from the CM 131 to the BEPK 140 and performsthe processes S8140 and S8150, as in the normal write process.

The MP 121 then clears the process stage information items.

The above is the second specific example of the transition writeprocess. In the present embodiment, it is guaranteed that the new parityis written into the physical page of the parity FMPK 144P as long as theprocess stage information item indicates the post-parity generationstage. Therefore, the MP 121 that carries out the transition process cantake over the write process, from the point where the new user data iswritten (S8140), and complete the write process.

According to this embodiment, the other MPs 121 can take over the writeprocess to perform the transition write process, even when the MP faultoccurs in the pre-parity generation stage or the post-parity generationstage. Similarly, data loss does not occur even when the simultaneouspoint of fault occurs in the plurality of MPPKs 120, the plurality ofCMPKs 130, the plurality of BEPKs 140 and the plurality of FMPKs 144.

Write Process to FMPK 144 According to Embodiment 4

The FMPK states in the aforementioned write process are now describedhereinafter.

The FMPK 144 here is the same as the parity FMPK 144P.

FIG. 71 shows a state of the parity FMPK 144P in the FMPK state 1aaccording to Embodiment 4. In the following description, the logicalpage that is designated by a command sent from the controller 100 to theparity FMPK 144P is referred to as “target logical page.” Of the entriesof the pointer table shown in the memory 1445 of the FMPK 144, the entrycorresponding to the target logical page is referred to as “target entry1449.” The target entry 1449 has a field for a logical page address,which is a logical address designating the target logical page, a fieldfor an old physical page address, which is a physical addressdesignating an old physical page, a field for a new physical pageaddress, which is a physical address designating a new physical page,and a field for a temporary physical page address, which is a physicaladdress designating a temporary physical page. In the diagram and thefollowing description, in the target entry 1449, the logical pageaddress is called “LA,” the old physical page address “oPA,” the newphysical page address “nPA,” and the temporary physical page address“tPA.” In addition, the value of the logical page address is describedas “LBA xxxx,” and the values of the old physical page address, the newphysical page address, and the temporary physical page address aredescribed as “p0,” “p1,” “p2,” “p3,” and “p4.”

In the parity FMPK 144P under the FMPK state 1a, the old parity isstored in the old physical page. Furthermore, the logical page addressand the old physical page address are associated with each other andstored in the target entry 1449.

FIG. 72 shows an FMPK state 2a according to Embodiment 4. In the parityFMPK 144P under the FMPK state 2a, the old parity is stored in the oldphysical page, and the old user data is stored in the temporary physicalpage. The correspondence relationship among the logical page address,the old physical page address, and the temporary physical page addressis stored in the target entry 1449.

FIG. 73 shows an FMPK state 3a according to Embodiment 4. In the parityFMPK 144P under the FMPK state 3a, the old data is stored in the oldphysical page, the old user data is stored in the temporary physicalpage, and the new parity in the new physical page. The correspondencerelationship among the logical page address, the old physical pageaddress, the temporary physical page address, and the new physical pageaddress is stored in the target entry 1449.

Operations by FMPK 144 Based on Commands, According to Embodiment 4

Next are described operations that are performed in Embodiment 4 by theFMPK 144 under the FMPK states and based on commands upon the occurrenceof system faults under the FMPK states.

FIG. 74 shows an operation performed based on the old data transmissioncommand under the FMPK state 1a, according to Embodiment 4. First, theparity FMPK 144P receives the old data transmission command from theBEPK 140 of the controller 100 (S9110). This old data transmissioncommand accompanies the old user data. The parity FMPK 144P then writesthe old user data into the temporary physical page different from theold physical page (S9120). Next, the parity FMPK 144P performs thepointer connection on the old user data by designating the temporaryphysical page for the temporary physical page address of the targetentry 1449 (S9130). The parity FMPK 144P then sends a normal endresponse to the controller 100 (S9140). With the old data transmissioncommand, the parity FMPK 144P can write the received data into thephysical page different from the old parity, without overwriting thedata into the old parity. As a result of transmitting the old datatransmission command to the parity FMPK in the FMPK state 1a, the FMPKstate transits to the FMPK state 2a.

FIG. 75 shows an operation performed by the parity FMPK 144P under theFMPK state 2a based on the old data transmission command, according toEmbodiment 4. First, the parity FMPK 144P receives the old datatransmission command from the BEPK 140 of the controller 100 (S9210).This old data transmission command accompanies the old user data. Theparity FMPK 144P then secures an additional temporary physical page,which is a physical page different from the temporary physical page, andwrites the old user data into the additional temporary physical page(S9220). Subsequently, the parity FMPK 144P performs the pointerreplacement for replacing the first temporary data of the temporaryphysical page with the first temporary data of the additional temporaryphysical page, by designating the additional temporary physical page forthe temporary physical page address of the target entry 1449 (S9230).The parity FMPK 144P then sends a normal end response to the controller100 (S9240). This process is carried out during the transition writeprocess when a fault occurs after the transmission of the old data(S8120) in the pre-parity generation stage. In other words, even whenthe old data transmission command is transmitted to the parity FMPK inthe FMPK state 2a, the state same as the FMPK state 2a can be obtained.

FIG. 76 shows an operation performed based on the old data transmissioncommand in the parity FMPK 144P under the state 3a, according toEmbodiment 4. First, the FMPK 144 receives the old data transmissioncommand from the BEPK 140 of the controller 100 (S9310). This old datatransmission command accompanies the first temporary data. The parityFMPK 144P then writes the first temporary data into the additionaltemporary physical page (S9320). Subsequently, the parity FMPK 144Pperforms the pointer replacement for replacing the first temporary dataof the temporary physical page with the first temporary data of theadditional temporary physical page, by designating the additionaltemporary physical page for the temporary physical page address of thetarget entry 1449 (S9330). Then, the parity FMPK 144P sends a normal endresponse to the controller 100 (S9340). This process is carried outduring the transition write process when a fault occurs after thetransmission of the new data (S8130) in the pre-parity generation stage.In other words, even when the old data transmission command istransmitted to the parity FMPK in the FMPK state 3a, the state same asthe FMPK state 3a can be obtained.

FIG. 77 shows an operation performed based on the new data transmissioncommand under the FMPK state 1a, according to Embodiment 4. First, theparity FMPK 144P receives the new data transmission command from theBEPK 140 of the controller 100 (S9410). This new data transmissioncommand accompanies second temporary data. The second temporary data isthe same as the new user data obtained in the aforementioned writeprocess. The FMPK 144 then sends an abnormal end response to thecontroller 100 (S9420).

FIG. 78 shows an operation performed based on the new data transmissioncommand under the FMPK state 2a, according to Embodiment 4. First, theparity FMPK 144P receives the new data transmission command from theBEPK 140 of the controller 100 (S9510). This new data transmissioncommand accompanies the new user data. The FMPK 144 then writes the newuser data into the memory 1445 (S9520). Next, the FMPK 144 reads the oldparity in the old physical page and old user data in the temporaryphysical page, and the new user data stored in the memory 1445,generates the new parity by means of the XOR circuit 1442, and writesthe new data into the new physical page (S9530). Subsequently, the FMPK144 performs the pointer connection on the new parity by designating thenew physical page for the new physical page address of the target entry1449 (S9540). The FMPK 144 then sends a normal end response to thecontroller 100 (S9550). As a result of transmitting the new datatransmission command to the parity FMPK in the FMPK state 2a, the FMPKstate transits to the FMPK state 3a.

FIG. 79 shows an operation performed based on the new data transmissioncommand under the FMPK state 3a, according to Embodiment 4. First, theparity FMPK 144P receives the new data transmission command from theBEPK 140 of the controller 100 (S9610). This new data transmissioncommand accompanies the new user data. The FMPK 144 then writes the newuser data into the memory 1445 (S9620). The parity FMPK 144P then readsthe old data stored in the old physical page, the old user data storedin the temporary physical page, and the new user data stored in thememory 1445, generates the new data by means of the XOR circuit 1442,secures an additional physical page, which is a physical page differentfrom the new physical page, and writes the new data into the additionalphysical page (S9630). Subsequently, the parity FMPK 144P performs thepointer replacement for replacing the new data stored in the newphysical page with the new data stored in the additional physical page,by designating the additional physical page for the new physical pageaddress of the target entry 1449 (S9640). Subsequently, the parity FMPK144P sends a normal end response to the controller 100 (S9650). Thisprocess is carried out during the transition write process, subsequentto the one shown in FIG. 76, when a fault occurs after the transmissionof the new data (S8130) in the pre-parity generation stage. In otherwords, even when the old data transmission command is transmitted to theparity FMPK in the FMPK state 3a, the same FMPK state 3a can beobtained.

In this manner, regardless of the presence/absence of a system fault,the MP 121 can change the FMPK state to the FMPK state 3a by issuing thecommand from the old data reading process, as long as the process stageinformation item indicates the pre-parity generation stage.

FIG. 80 shows an operation performed based on the new data commitcommand under the state 1a, according to Embodiment 4. First, the parityFMPK 144P receives the new data commit command from the BEPK 140 of thecontroller 100 (S9710). The new data commit command designates thelogical page in which the new data is stored. The parity FMPK 144P thensends a normal end response to the controller 100 (S9720). This processis carried out during the transition write process when a fault occursafter the transmission of the new data commit command (S8150) in thepost-parity generation stage.

FIG. 81 shows an operation performed based on the new data commitcommand under the state 2a, according to Embodiment 4. First, the parityFMPK 144P receives the new data commit command from the BEPK 140 of thecontroller 100 (S9810). This new data commit command designates thelogical page having the new data stored therein. The parity FMPK 144Pthen sends an abnormal end response to the controller 100 (S9820).

FIG. 82 shows an operation performed based on the new data commitcommand under the state 3a, according to Embodiment 4. First, the parityFMPK 144P receives the new data commit command from the BEPK 140 of thecontroller 100 (S9910). This new data commit command designates thelogical page in which the new data is stored. The parity FMPK 144P thenperforms the pointer replacement for replacing the old data stored inthe old physical page with the new data stored in the new physical page,by designating the new physical page for the old physical page addressof the target entry 1449, and performs the pointer deletion on the firsttemporary data stored in the temporary physical page, by clearing thetemporary physical page address (S9920). Next, the parity FMPK 144Psends a normal end response to the controller 100 (S9930). As a resultof this process, the state can transit to a state in which the newparity is determined in the parity FMPK 144P, even upon the occurrenceof a fault prior to the transmission of the new data commit command inthe post-parity generation stage. In this manner, defining each of thecommands can allow the process to be taken over even upon the occurrenceof a system fault and prevent the occurrence of data loss. In addition,in the present embodiment, when the process stage information itemindicates the two stages, “pre-parity generation stage” and “post-paritygeneration stage,” the process is taken over upon the occurrence of afault, whereby the number of accesses to the SM 132 for recording theprocess stage information item therein and the access load can bereduced.

Embodiment 5

This embodiment has the same functions as those described in Embodiment2 but illustrates a situation where the XOR circuit 1442 of the FMPK 144supports only an XPWRITE function of the SCSI command. Furthermore, inthe present embodiment, the process stage information item stored in theSM 132 indicates the pre-parity generation stage, the stage in processof parity media update, and the post-parity generation stage.

Write Process According to Embodiment 5

A normal write process is now described hereinafter.

FIG. 83 shows a write process according to Embodiment 5. In thissequence diagram, the DFa and DFb of the data FMPK 144A represent thememory 1445 and the FM 1443 (physical page) of the data FMPK 144A. Also,the DFa and the DFb of the parity FMPK 144P represent the memory 1445and the FM 1443 (physical page) of the parity FMPK 144P. The keycomponents of the operations shown in this sequence diagram are the sameas those shown in the sequence diagrams related to the write processaccording to Embodiment 2.

First, the MP 121 performs the processes S2110 to S2350, as in the writeprocess according to Embodiment 1. The MP 121 accordingly changes thevalues of the process stage information items of the two SMs 132corresponding to the regions of the two CMs 131 having the new user datastored therein, to the pre-parity generation, as in the write processaccording to Embodiment 1.

The MP 121 then performs the process S8110, as in the write processaccording to Embodiment 4. Consequently, the BEPK 140 receives the olduser data from the data FMPK 144A and writes the old user data into thebuffer 143. The MP 121 accordingly changes the value of each processstage information to the parity media update.

Subsequently, the MP 121 sends the XPWRITE command to the parity FMPK144P (S8320). This XPWRITE command designates the logical page havingthe old parity stored therein, and accompanies the old user data. Atthis moment, in response to an instruction from the MP 121, the BEPK 140reads the old user data from the buffer 143, and sends the old user datato the parity FMPK 144P.

Subsequently, the parity FMPK 144P receives the XPWRITE command and theold user data from the controller 100. The parity FMPK 144P accordinglywrites the old user data into the memory 1445, reads the old parity fromthe FM 1443, reads the old user data from the memory 1445, generates theintermediate parity using the XOR circuit 1442, and writes theintermediate parity into the memory 1445 of the FM 1443. The parity FMPK144P then notifies the controller 100 of a normal end of the XPWRITEcommand.

Subsequently, the MP 121 is notified by the parity FMPK 144P of thenormal end of the XPWRITE command.

Accordingly, the MP 121 sends the XPWRITE command to the parity FMPK144P (S8330). This XPWRITE command designates the physical address ofthe memory 1445 having the intermediate parity stored therein, andaccompanies the new user data. At this moment, in response to aninstruction from the MP 121, the BEPK 140 reads the new user data fromthe CM 131, writes the new user data into the buffer 143, reads the newuser data from the buffer 143, and sends the new user data to the parityFMPK 144P.

Next, the parity FMPK 144P receives the XPWRITE command and the new userdata from the controller 100. The parity FMPK 144P accordingly writesthe new user data into the memory 1445, reads the intermediate parityfrom the memory 1445, reads the new user data from the memory 1445,generates the new parity from the intermediate parity and the new userdata by means of the XOR circuit 1442, and writes the new parity intothe FM 1443. The parity FMPK 144P then notifies the controller 100 of anormal end of the XPWRITE command.

Subsequently, the MP 121 is notified by the parity FMPK 144P of thenormal end of the XPWRITE command. The MP 121 accordingly changes thevalue of each process stage information item to the post-paritygeneration stage.

The MP 121 then sends the normal write command to the data FMPK 144A(S8340). This normal write command accompanies the new user data.

The data FMPK 144A then receives the normal write command and the newuser data from the controller 100. The data FMPK 144A accordingly writesthe new user data into the FM 1443 and notifies the controller 100 of anormal end of the normal write command.

Subsequently, the MP 121 is notified by the data FMPK 144A of the normalend of the normal write command. The MP 121 accordingly clears the valueof each process stage information item.

The Above is the Write Process.

In this manner, the controller 100 sends the old user data from thebuffer 143 to the parity FMPK 144P without writing the old user datareceived from the data FMPK 144A into the CM 131. As a result, thenumber of accesses to the CM 131 during the write process is reduced,thereby the number of accesses to the CM 131 can be reduced.

Moreover, according to this embodiment, the reliability of the storagesystem 10 can be improved by storing the new user data and each processstage information item into the two CMPKs 130.

Specific Examples of Transition Write Process According to Embodiment 5

Several specific examples of a transition write process performed uponthe occurrence of an MP fault are described hereinafter.

First Specific Example of Transition Write Process According toEmbodiment 5

Here is described a transition write process that is performed upon theoccurrence of an MP fault in the pre-parity generation stage.

FIG. 84 shows the transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 5. The operation targets shown in this sequence diagram arethe same as those illustrated in the sequence diagrams related to thenormal write process.

Once the MP 121 free of faults recognizes a fault in another MP 121, theMP 121 acknowledges that the process stage information item indicatesthe pre-parity generation stage. Accordingly, the MP 121 performs theprocesses S8110 to S8340, as in the normal write process. In otherwords, when the process stage information item indicates the pre-paritygeneration stage, the MP 121 takes over the write process, from thepoint where the old user data is transmitted from the data FMPK 144A tothe buffer 143 of the BEPK 140.

Subsequently, the MP 121 clears the process stage information itemstored in the SM 132.

The above is the transition write process.

Second Specific Example of Transition Write Process According toEmbodiment 5

Here is described a transition write process that is performed upon theoccurrence of the MP fault in the mid-stage of parity media update.

FIG. 85 shows the transition write process performed upon the occurrenceof the MP fault in the mid-stage of parity media update, according toEmbodiment 5. The key operation targets illustrated in this sequencediagram are the same as those shown in the sequence diagrams related tothe normal write process.

Once the MP 121 free of faults recognizes the fault occurring in anotherMP, the MP 121 acknowledges that the process stage information itemsindicate the mid-stage of parity media update. Accordingly, the MP 121performs the processes S6510 and S6520, as in the transition writeprocess that is performed upon the occurrence of the MP fault in themid-stage of parity media update according to Embodiment 2 (see FIG.56). In other words, the MP 121 free from faults takes over a writeprocess from a process of generating a new parity.

The MP 121 then sends the normal write command to the parity FMPK 144P(S8360). This normal write command accompanies the new parity.Consequently, the BEPK 140 writes the new parity stored in the CM 131into the buffer 143, and sends the new parity to the parity FMPK 144P.The parity FMPK 144P accordingly writes the new parity into the FM 1443.

Subsequently, the MP 121 is notified by the parity FMPK 144P of a normalend of the normal write command. The MP 121 accordingly changes thevalue of each process stage information item to the post-paritygeneration.

The MP 121 then sends the normal write command to the data FMPK 144A(S8370). The normal write command accompanies the new user data.Consequently, the BEPK 140 writes the new user data stored in the CM 131into the buffer 143, and sends the new user data to the data FMPK 144A.The data FMPK 144A accordingly writes the new user data into the FM1443.

Subsequently, the MP 121 clears each process stage information itemstored in the SM 132.

The above is the transition write process.

Third Specific Example of Transition Write Process According toEmbodiment 5

Here is described a transition write process that is performed upon theoccurrence of the MP fault in the post-parity generation stage.

FIG. 86 shows a transition write process performed upon the occurrenceof the MP fault in the post-parity generation, according to Embodiment5. The key components of the operations illustrated in this sequencediagram are the same as those shown in the sequence diagrams related tothe normal write process.

Once the MP 121 free of faults recognizes the MP fault, the MP 121acknowledges that the process stage information items indicate thepost-parity generation. Accordingly, the MP 121 performs the processS8370, as in the aforementioned transition write process that isperformed upon the occurrence of the MP fault in the parity mediaupdate. In other words, the MP 121 free of faults takes over the writeprocess, from the point where the normal write command is sent to thedata FMPK 144A (S8370).

Subsequently, the MP 121 clears the process stage information itemstored in the SM 132.

The above is the transition write process.

According to these transition write processes (the first specificexample to the third specific example), even when the MP fault occurs inthe pre-parity generation stage, the stage in process of parity mediaupdate, or the post-parity generation stage, which are indicated by theprocess stage information item, in the present embodiment another MP 121free of faults can take over the write process to perform the transitionwrite process. Similarly, data loss does not occur in the presentembodiment even when the simultaneous point of fault occurs in theplurality of MPPKs 120, the plurality of CMPKs 130, and the plurality ofBEPKs 140. Therefore, the reliability of the storage system 10 can beimproved.

In addition, this embodiment can realize the same functions as thosedescribed in Embodiment 2, by using the XPWRITE function of the FMPK144.

Embodiment 6

This embodiment has the same configurations as those described inEmbodiment 5, and illustrates a situation where the reliability of thestorage system 10 is improved more than by Embodiment 5. In thisembodiment, the process stage information item stored in the SM 132indicates the pre-parity generation stage, the stage in process ofparity media update, and the post-parity generation stage.

Write Process According to Embodiment 6

A normal write process is described hereinafter.

FIG. 87 shows a write process according to Embodiment 6. The operationtargets illustrated in this sequence diagram are the same as those shownin the sequence diagrams related to the write process according toEmbodiment 2.

First, the MP 121 performs the processes S2110 to S2350, as in the writeprocess according to Embodiment 1. The MP 121 accordingly changes thevalues of the process stage information items of the two SMs 132corresponding to the two CMs 131 having the new user data storedtherein, to the pre-parity generation.

The MP 121 then performs the process S6310, as in the write processaccording to Embodiment 3. Accordingly, the old parity stored in theparity FMPK 144P is written to the buffer 143.

Subsequently, the MP 121 performs the process S8110, as in the writeprocesses according to Embodiment 4 and Embodiment 5. Accordingly, theold user data stored in the data FMPK 144A is written to the buffer 143.The MP 121 accordingly changes the value of each process stageinformation item to the of parity media update.

The MP 121 then performs the processes S8320 to S8340, as in the writeprocess according to Embodiment 5. Accordingly, the intermediate parityis generated in the parity FMPK 144P and written to the memory 1445.Additionally, the new user data stored in the CM 131 is written into thebuffer 143. The new parity is generated in the parity FMPK 144P andwritten into the FM 1443.

Accordingly, the MP 121 clears each process stage information itemstored in the SM 132.

The Above is the Write Process.

In this manner, the controller 100 sends the old user data from thebuffer 143 to the parity FMPK 144P without writing the old user datareceived from the data FMPK 144A into the CM 131. As a result, thenumber of accesses to the CM 131 during the write process is reduced.

Furthermore, according to this embodiment, the reliability of thestorage system 10 can be improved by storing the new user data, eachprocess stage information, and the old parity in the two CMPKs 130.

Specific Examples of Transition Write Process According to Embodiment 6

Several specific examples of a transition write process performed uponthe occurrence of an MP fault are now described hereinafter.

First Specific Example of Transition Write Process According toEmbodiment 6

Here is described a transition write process that is performed upon theoccurrence of an MP fault in the pre-parity generation stage.

FIG. 88 shows a transition write process performed upon the occurrenceof the MP fault in the pre-parity generation stage, according toEmbodiment 6. The operation targets illustrated in this sequence diagramare the same as those shown in the sequence diagrams related to thenormal write process.

Once the MP 121 free of faults recognizes a fault occurring in anotherMP 121, the MP 121 acknowledges that the process stage information itemindicates the pre-parity generation stage. Accordingly, the MP 121performs the processes S6310 to S8340, as in the normal write process.In other words, the MP 121 free of faults takes over the write process,from the point where the old parity stored in the parity FMPK 144P iswritten to the buffer 143.

The MP 121 accordingly clears the process stage information item storedin the SM 132.

The above is the transition write process.

Second Specific Example of Transition Write Process According toEmbodiment 6

Here is described a transition write process that is performed upon theoccurrence of the MP fault in the mid-stage of parity media update.

FIG. 89 shows a transition write process performed upon the occurrenceof the MP fault in the mid-stage in process of parity media update,according to Embodiment 6. The key components of the operationsillustrated in this sequence diagram are the same as those shown in thesequence diagrams related to the normal write process.

Once the MP 121 free of faults recognizes a fault occurring in anotherMP 121, the MP 121 acknowledges that the process stage information itemindicates the stage in process of parity media update. Accordingly, theMP 121 sends the normal write command to the parity FMPK 144P (S8210).In other words, the MP 121 free of faults takes over the write process,from the point where the normal write command is sent to the parity FMPK144P. This normal write command accompanies the old parity.Consequently, the BEPK 140 writes the old parity stored in the CM 131into the buffer 143, and sends the old parity to the parity FMPK 144P.Accordingly, the parity FMPK 144P writes the old parity into the FM1443.

The MP 121 is then notified by the parity FMPK 144P of a normal end ofthe normal write command. Accordingly, the MP 121 sends the XPWRITEcommand to the parity FMPK 144P (S8220). This normal write commandaccompanies the old user data. Accordingly, the BEPK 140 writes the olduser data stored in the CM 131 into the buffer 143, and sends the olduser data to the data FMPK 144A. The parity FMPK 144P accordingly writesthe old user data into the memory 1445, generates the intermediateparity from the old parity stored in the FM 1443 and the old user datastored in the memory 1445, and writes the intermediate parity into theFM 1443.

Subsequently, the MP 121 is notified by the parity FMPK 144P of a normalend of the XPWRITE command. The MP 121 accordingly performs the S8330and S8340, as in the normal write process.

Accordingly, the MP 121 clears each process stage information itemstored in the SM 132.

The above is the transition write process.

Third Specific Example of Transition Write Process According toEmbodiment 6

Here is described a transition write process that is performed upon theoccurrence of an MP fault in the post-parity generation stage.

FIG. 90 shows a transition write process performed upon the occurrenceof the MP fault in the post-parity generation stage, according toEmbodiment 6. The operation targets illustrated in this sequence diagramare the same as those shown in the sequence diagrams related to thenormal write process.

Once the MP 121 free of faults recognizes a fault has occurred in the MP121, the MP 121 acknowledges that the process stage information itemsindicate the post-parity generation stage. Accordingly, the MP 121 thensends the normal write command to the data FMPK 144A (S8230). The MP 121free of faults takes over the write process, from the point where thenormal write command is sent to the data FMPK 144A. This normal writecommand accompanies the new user data.

Subsequently, the data FMPK 144A receives the normal write command andthe new user data from the controller 100. The data FMPK 144Aaccordingly writes the new user data stored in the CM 131 into the FM1443, and notifies the controller 100 of a normal end of the normalwrite command.

Subsequently, the MP 121 is notified by the data FMPK 144A of the normalend of the normal write command. The MP 121 accordingly clears the valueof each process stage information item stored in the SM 132.

The above is the transition write process.

According to these transition write processes (first to third specificexamples), even when the MP fault occurs in the pre-parity generationstage, the mid-stage of the parity media update, or the post-paritygeneration stage, the other MPs 121 free from faults can take over thewrite process to perform the transition write process. Similarly, dataloss does not occur even when the simultaneous point of fault occurs inthe plurality of MPPKs 120, the plurality of CMPKs 130, the plurality ofBEPKs 1440, and the plurality of FMPKs 144. Therefore, the reliabilityof the storage system 10 can be improved.

This embodiment can realize the same functions as those described inEmbodiment 2, by using the XPWRITE function of the FMPK 144. Moreover,this embodiment can improve the reliability of the storage system 10better than by Embodiment 5, by writing the old parity into the two CMs131.

Embodiment 7

This embodiment illustrates a situation where Embodiment 1 is applied toRAID level 6.

The controller 100 uses the plurality of FMPKs 144 to construct a RAIDgroup of RAID level 6. This RAID group uses a Reed-Solomon method. A Pparity and Q parity are obtained by the following formulae by using theuser data D[0], D[1], . . . , D[n−1], and Q parity generationcoefficients A[0], A[1], A[n−1]:P=D[0]+D[1]+ . . . +D[n−1]  (Ep)Q=A[0]*D[0]+A[1]*D[1]+ . . . +A[n−1]*D[n−1]  (Eq)

The memory 1445 of the FMPK 144 has A[i] stored therein, where i is adata row number within the stripe (i=0, 1, . . . , n−1). A[i] may bestored in the XOR circuit 1442.

Write Process According to Embodiment 7

A normal write process is now described hereinafter.

In the diagrams, the write process according to Embodiment 7 is dividedinto a first process and a second process. FIG. 91 shows the firstprocess of the write process according to Embodiment 7. FIG. 92 showsthe second process of the write process according to Embodiment 7.

In the following description, the P parity generated from the old userdata is referred to as “old parity,” the Q parity generated from the olduser data as “old Q parity,” the P parity generated from the new userdata as “new parity,” and the Q parity generated from the new user dataas “new Q parity.”

In the following description, of the plurality of FMPKs 144 configuringthe RAID group, the FMPK 144 having the old party stored therein isreferred to as “parity FMPK 144P,” and the FMPK 144 having the old Qparity stored therein is referred to as “parity FMPK 144Q.” Theconfigurations other than that of the parity FMPK 144Q in the storagesystem 10 are the same as those described in Embodiment 1. Thecontroller 100 sends information indicating the data row number to theparity FMPK 144Q so that the parity FMPK 144Q specifies the A[i].

In this embodiment, a Q parity intermediate parity transmission commandis newly defined as the I/O command sent from the controller 100 to theFMPK 144.

Each of the operation targets illustrated in the sequence diagram of thefirst process are the same as each of the operation targets illustratedin the sequence diagram related to the write process according toEmbodiment 1. The operation targets illustrated in the sequence diagramof the second process are, in addition to the operation targetsillustrated in the sequence diagram of the first process, the port 1441within the parity FMPK 144Q, the XOR circuit 1442 within the parity FMPK144Q, and storage media QFa and QFb within the parity FMPK 144Q. Thestorage media QFa and QFb of the parity FMPK 144Q respectively representtwo physical pages stored in the FM 1443.

The first process of the write process is described hereinafter.

First, MP 121 performs the processes S2110 to S3120, as in the writeprocess according to Embodiment 1. Accordingly, the buffer 143 of theBEPK 140 has the intermediate parity stored therein. Furthermore, the FM1443 of the parity FMPK 144P has the old parity and the new paritystored therein.

The second process of the write process is described hereinafter.

Subsequently, the MP 121 sends the Q parity intermediate paritytransmission command to the parity FMPK 144Q (S9110). This Q parityintermediate parity transmission command designates the logical pagehaving the old Q parity stored therein, and accompanies the intermediateparity and the data row number. At this moment, in response to aninstruction from the MP 121, the BEPK 140 reads the intermediate parityfrom the buffer 143, and sends the intermediate parity to the parityFMPK 144Q.

The parity FMPK 144Q then receives the Q parity intermediate paritytransmission command, the intermediate parity, and the data row numberfrom the controller 100. The parity FMPK 144Q accordingly writes theintermediate parity into the memory 1445, reads the old Q parity storedin the FM 1443, reads the intermediate parity stored in the memory 1445,reads the Q parity generation coefficient stored in the memory 1445 onthe basis of the data row number, generates the new Q parity by means ofthe XOR circuit 1442, and writes the new parity Q into the FM 1443. Theparity FMPK 144Q then notifies the controller 100 of a normal end of theQ parity intermediate parity transmission command.

Subsequently, the MP 121 is notified by the parity FMPK 144Q of thenormal end. The MP 121 accordingly changes the value of each processstage information item to the post-parity generation stage.

The MP 121 then sends the new data commit command to the parity FMPK144P (S9120). This new data commit command designates the logical pagehaving the new user data stored therein.

Then, the data FMPK 144A receives the new data commit command from thecontroller 100. Accordingly, the data FMPK 144A determines the new userdata as the user data after update, and notifies the controller 100 of anormal end of the new data commit command.

Subsequently, the MP 121 is notified by the data FMPK 144A of the normalend of the new data commit command. Accordingly, the MP 121 sends thenew data commit command to the parity FMPK 144P (S9230). This new datacommit command designates the logical page having the new parity storedtherein.

The parity FMPK 144P then receives the new data commit command from thecontroller 100. Accordingly, the parity FMPK 144P determines the newparity as the P parity after update, and notifies the controller 100 ofa normal end of the new data commit command.

Subsequently, the MP 121 is notified by the parity FMPK 144P of thenormal end of the new data commit command. The MP 121 accordingly sendsthe new data commit command to the parity FMPK 144Q (S9240). This newdata commit command designates the logical page having the new Q paritystored therein.

The parity FMPK 144Q then receives the new data commit command from thecontroller 100. Accordingly, the parity FMPK 144Q determines the new Qparity as the Q parity after update, and notifies the controller 100 ofa normal end of the new data commit command.

Subsequently, the MP 121 is notified by the parity FMPK 144Q of thenormal end of the new data commit command. Accordingly, the MP 121clears the value of each process stage information item stored in the SM132.

The above is the write process.

In this manner, the controller 100 sends the intermediate parity fromthe buffer 143 to the parity FMPK 144P and the parity FMPK 144Q withoutwriting the intermediate parity received from the data FMPK 144A intothe CM 131. As a result, the number of accesses to the CM 131 during thewrite process is reduced.

In addition, as with Embodiment 1, data loss does not occur even whenthe simultaneous point of fault occurs in the plurality of MPPKs 120,the plurality of CMPKs 130, the plurality of BEPKs 140, and theplurality of FMPKs 144. Therefore, the reliability of the storage system10 can be improved.

According to each of the embodiments described above, reducing thenumber of accesses to the CM 131 can reduce the communication overheadof the communication with the CMPK 130 and the load on the CM 131,improving the throughput of the storage system 10.

According to each of the embodiments described above, the reliability ofthe storage system 10 can be improved by storing the new user data andeach process stage information item in the two CMPKs 130.

Furthermore, according to each of the embodiments described above, theoccurrence of data loss can be prevented even when the simultaneouspoint of fault occurs in the plurality of MPPKs 120, the plurality ofCMPKs 130, and the plurality of BEPKs 140 during the write processes.

In each of the embodiments described above, hamming codes, redundancycodes and the like may be used in place of the parities.

Moreover, the order of the steps of the operations performed by thecontroller 100 is often changed. For instance, S3230 and S3320 can beswitched over. Additionally, S8120 and S8310 can be switched over aswell.

Each logical region group may be in the form of a stripe based on theRAID group. Each logical region may be an element configuring thestripe, or may be provided one-on-one to a nonvolatile memory. Eachlogical region group may be a component of a logical unit provided to atransmission-source device to which a write request is transmitted(e.g., the host computer or another storage system), or may be a regiongroup (a region group that is allocated to a write-destination virtualsegment, when writing occurs on the virtual segment) that is dynamicallyallocated to any of a plurality of virtual segments (virtual storageregions), which configure a virtual logical unit (e.g., a logical unitaccording to thin provisioning) provided to the transmission-sourcedevice. In the latter case, a storage region pool may be configured bythe plurality of logical segments. Each logical segment may beconfigured by one or more logical region groups and allocated to avirtual segment in units of the logical segments. The storage regionpool may be configured by a plurality of logical units, in which caseeach of the logical units may be configured by two or more logicalsegments.

The present specification has described, for example, the followingstorage systems according to (Description 1) to (Description 4).

(Description 1)

A storage system, comprising:

-   -   a plurality of storage devices, each of which has a plurality of        storage media and a device controller for controlling the        plurality of storage media and has a RAID group configured by        the plurality of storage media; and    -   a system controller that has a processor, a buffer memory        coupled to the plurality of storage devices and the processor by        a predetermined communication network, and a cache memory        coupled to the processor and the buffer memory by the        predetermined communication network,    -   wherein the processor stores first data, which is related to a        write request from a host computer, in the cache memory,        specifies from the plurality of storage devices a first storage        device for storing data before update, which is data obtained        before updating the first data, and transfers the first data to        the specified first storage device,    -   a first device controller of the first storage device transmits        the first data and second data based on the data before update,        from the first storage device to the system controller, and    -   the processor stores the second data in the buffer memory,        specifies a second storage device from the plurality of storage        devices, transfers the stored second data to the specified        second storage device, and manages a process stage information        item indicating a stage of a process performed on the write        request.

(Description 2)

The storage system according to Description 1,

-   -   wherein the second data is an intermediate parity and the second        storage device is a storage device in which parity data before        update is stored,    -   the first device controller calculates the intermediate parity        based on the first data and the data before update that are        stored in the first storage device, and transmits the calculated        intermediate parity to the system controller,    -   the processor stores the intermediate parity in the buffer        memory and transfers the stored intermediate parity to the        second storage device, and    -   a second device controller of the second storage device        calculates an updated parity based on the transferred        intermediate parity and a parity before update, and writes the        calculated updated parity into the second storage device.

(Description 3)

The storage system according to Description 2,

-   -   wherein each of the storage media is a flash memory,    -   the data before update is stored in a first physical region of        the flash memory, and    -   the first device controller stores the first data in a second        physical region different from the first physical region of the        flash memory, and keeps a correspondence relationship between        the data before update and the first physical region and a        correspondence relationship between the first data and the        second physical region until the updated parity is stored in a        flash memory of the second storage device.

(Description 4)

The storage control apparatus according to Description 4,

-   -   wherein the first device controller allocates the first physical        region storing the data before update to a first logical region        designated by a write request, and writes first data obtained        from the second memory into the second physical region, which is        a physical region different from the first physical region in        the first storage device, and    -   after the updated parity is written to the second storage        device, the first device controller allocates the second        physical region to the first logical region.

In these descriptions, the system controller and additional systemcontroller correspond to, for example, the MPs 121. Each devicecontroller corresponds to, for example, the CPU 1444 of the FMPK 144.Each storage device corresponds to, for example, the FM 1443 of the FMPK144. The first memory corresponds to, for example, the SM 132. The firstdata corresponds to, for example, the new user data. The second datacorresponds to, for example, the intermediate parity or the old userdata.

REFERENCE SIGNS LIST

-   10 Storage system-   100 Controller-   112 Transfer circuit-   113 Buffer-   123 Internal path-   142 Transfer circuit-   143 Buffer-   150 Communication network-   200 Storage unit-   1441 Port-   1442 Logical operation circuit-   1443 FM (Flash Memory)-   1444 CPU (Central Processing Unit)-   1445 Memory    -   1446 Disk I/F

The invention claimed is:
 1. A storage system comprising: a plurality offlash memory packages, and a system controller including: a processorconfigured to manage the plurality of flash memory packages as a RAIDgroup, the plurality of flash memory packages including a first flashmemory package storing old data and a second flash memory packagestoring old parity related to the old data, a cache memory coupled tothe processor in which data stored in the cache memory remains after aparticular process is completed and is reused by another process, and abuffer memory coupled to the processor, the cache memory and theplurality of flash memory packages, where data stored in the buffermemory is deleted after another particular process is completed, whereinthe processor is configured to: store new data, which is sent from ahost computer into the cache memory; transfer the new data from thecache memory to the first flash memory package storing old data togenerate intermediate parity which is based on the new data and the olddata, transfer the intermediate parity to the second flash memorypackage storing old parity via the buffer memory without storing theintermediate parity into the cache memory to generate new parity whichis based on the intermediate parity and the old parity, and delete theintermediate parity from the buffer memory according to receiving aresponse, from the second flash memory package, that indicates thetransfer of the intermediate parity is completed.
 2. A storage systemaccording to claim 1, wherein the first flash memory package includes afirst memory controller and a plurality of first flash memory chips, thefirst memory controller configured to: store the new data into one ofthe plurality of flash memory chips, generate the intermediate parityfrom the new data and the old data, and transfer the intermediate parityto the buffer memory, while the first memory controller maintains thenew data and the old data as a valid status.
 3. A storage systemaccording to claim 2, wherein the second flash memory package includes asecond memory controller and a plurality of second flash memory chips,the second memory controller configured to: generate the new parity fromthe intermediate parity and the old parity, and store the new parityinto one of the plurality of second flash memory chips.
 4. A storagesystem according to claim 3, wherein the processor is configured to senda commit command to the first flash memory package for invalidating theold data after storing the new parity into the one of the plurality ofsecond flash memory chips.
 5. A storage system according to claim 4,wherein the second memory controller stores the new parity into the oneof the plurality of second flash memory chips and sends a completionreply to the system controller, and the processor receives thecompletion reply and deletes the intermediate parity from the buffermemory.
 6. A storage system according to claim 5, wherein the processor,after receiving the completion reply, sends the commit command to thefirst flash memory package for invalidating the old data and sends thecommit command to the second flash memory package for invalidating theold parity.
 7. A storage system according to claim 6, wherein the newdata within the cache memory is maintained after receiving thecompletion reply.
 8. A storage system according to claim 7, wherein whenthe processor detects a failure of the buffer memory before the newparity is stored into the one of the plurality of second flash memorychips, the processor sends the new data which is maintained within thecache memory to the first flash memory package so that the first memorycontroller generates the intermediate parity from the received new dataand the old data.
 9. A storage system according to claim 7, wherein thesystem controller further includes another processor, and when theanother processor detects a failure of the processor before the newparity is stored into the one of the plurality of second flash memorychips, the another processor sends the new data which is maintainedwithin the cache memory to the first flash memory package so that thefirst memory controller generates the intermediate parity from thereceived new data and the old data.
 10. A storage system according toclaim 9, wherein when the another processor detects the failure of theprocessor after the new parity is stored into the one of the pluralityof second flash memory chips, the another processor sends the commitcommand to the first flash memory package for invalidating the old datastored within the one of the plurality of first flash memory chips. 11.A storage system according to claim 1, wherein different flash memorypackages in the RAID group are coupled to the system controller withdifferent data busses, respectively.
 12. A storage system comprising: aplurality of flash memory packages, each of which includes a pluralityof flash memory chips and a flash controller coupled to the flash memorychips, and a system controller including: a processor configured tomanage the plurality of flash memory packages as a RAID group, a cachememory coupled to the processor in which data stored in the cache memoryremains after a particular process is completed is reused by anotherprocess, and a buffer memory coupled to the processor, the cache memoryand the plurality of flash memory packages, the buffer memory is used totransfer any data among the plurality of flash memory packages, and datastored in the buffer memory is deleted after another particular processis completed, wherein the processor is configured to: store new data,which is sent from a host computer, into the cache memory; transfer thenew data from the cache memory to a first flash memory package of theplurality of flash memory packages to generate intermediate parity whichis based on the new data and old data stored in the first flash memorypackage, transfer the intermediate parity to a second flash memorypackage of the plurality of flash memory packages via the buffer memorywithout storing the intermediate parity into the cache memory togenerate new parity which is based on the intermediate parity and oldparity related to the old data stored in the second flash memorypackage, and delete the intermediate parity from the buffer memoryaccording to receiving a response, from the second flash memory package,that indicates the transfer of the intermediate parity is completed. 13.A storage system according to claim 12, wherein a first memorycontroller of the first flash memory package is configured to: store thenew data into one of a plurality of first flash memory chips of thefirst flash memory package, generate the intermediate parity from thenew data and the old data, and transfer the intermediate parity to thebuffer memory, while the first memory controller maintains the new dataand the old data as a valid status.
 14. A storage system according toclaim 13, wherein a second memory controller of the second flash memorypackage is configured to: generate the new parity from the intermediateparity and the old parity and store the new parity into one of theplurality of second flash memory chips.
 15. A storage system accordingto claim 14, wherein the processor is configured to send a commitcommand to the first flash memory package for invalidating the old dataafter storing the new parity into the one of a plurality of second flashmemory chips of the second flash memory package.
 16. A storage systemaccording to claim 15, wherein the second memory controller stores thenew parity into the one of the plurality of second flash memory chipsand sends a completion reply to the system controller, and the processorreceives the completion reply and deletes the intermediate parity fromthe buffer memory.
 17. A storage system according to claim 16, whereinthe processor, after receiving the completion reply, sends the commitcommand to the first flash memory package for invalidating the old dataand sends the commit command to the second flash memory package forinvalidating the old parity.
 18. A storage system according to claim 17,wherein the new data within the cache memory is maintained afterreceiving the completion reply.
 19. A storage system according to claim18, wherein when the processor detects a failure of the buffer memorybefore the new parity is stored into the one of the plurality of secondflash memory chips, the processor sends the new data which is maintainedwithin the cache memory to the first flash memory package so that thefirst memory controller generates the intermediate parity from thereceived new data and the old data.
 20. A storage system according toclaim 18, wherein the system controller further includes anotherprocessor, and when the another processor detects a failure of theprocessor before the new parity is stored into the one of the pluralityof second flash memory chips, the another processor sends the new datawhich is maintained within the cache memory to the first flash memorypackage so that the first memory controller generates the intermediateparity from the received new data and the old data.
 21. A storage systemaccording to claim 20, wherein when the another processor detects thefailure of the processor after the new parity is stored into the one ofthe plurality of second flash memory chips, the another processor sendsthe commit command to the first flash memory package for invalidatingthe old data stored within the one of the plurality of first flashmemory chips.
 22. A storage system according to claim 12, whereindifferent flash memory packages in the RAID group are coupled to thesystem controller with different data busses, respectively.